Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 16aca650bc0e2ba1f6c5d9615f58a652d1efa27ebf5280bf5fc5093868c12108

Tx prefix hash: 48b178058577bc8fe89bc6d4e9f19d4ff51ece2dfbdc0d2187705632668954be
Tx public key: c6e72fa3f7597eed12a0cc89732b1ea205610129ff37ea8a86f01ef0e2891f43
Timestamp: 1577394699 Timestamp [UCT]: 2019-12-26 21:11:39 Age [y:d:h:m:s]: 05:078:09:50:26
Block: 32454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1205788 RingCT/type: yes/0
Extra: 01c6e72fa3f7597eed12a0cc89732b1ea205610129ff37ea8a86f01ef0e2891f430211000000064943cd9f000000000000000000

1 output(s) for total of 479.145357304000 dcy

stealth address amount amount idx
00: 74eb71414c50d7fa951dd2022b70953f8a67f44dc6e8f691ec364682cae1caa0 479.145357304000 53975 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 32464, "vin": [ { "gen": { "height": 32454 } } ], "vout": [ { "amount": 479145357304, "target": { "key": "74eb71414c50d7fa951dd2022b70953f8a67f44dc6e8f691ec364682cae1caa0" } } ], "extra": [ 1, 198, 231, 47, 163, 247, 89, 126, 237, 18, 160, 204, 137, 115, 43, 30, 162, 5, 97, 1, 41, 255, 55, 234, 138, 134, 240, 30, 240, 226, 137, 31, 67, 2, 17, 0, 0, 0, 6, 73, 67, 205, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8