Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b745aa6e62387ee1c9e03e6793b9b495ece89b4387537e49ea47ec6cb6b3ed79

Tx prefix hash: 2f284453e5d975a000f8cee99a5baea5d58f4968b36201d0dcd5dde070905ee2
Tx public key: bab996e4fe399ba76c170740ddea5cb8aa2d5aed3424f9ff976b8fd60d0586cf
Timestamp: 1703341341 Timestamp [UCT]: 2023-12-23 14:22:21 Age [y:d:h:m:s]: 01:113:19:16:05
Block: 919448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342462 RingCT/type: yes/0
Extra: 01bab996e4fe399ba76c170740ddea5cb8aa2d5aed3424f9ff976b8fd60d0586cf02110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e6a4f55961211f5fbc100d810f2d31e35160f9ef9dd4bb84114738107c08f89 0.600000000000 1377120 of 15

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": 919458, "vin": [ { "gen": { "height": 919448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e6a4f55961211f5fbc100d810f2d31e35160f9ef9dd4bb84114738107c08f89" } } ], "extra": [ 1, 186, 185, 150, 228, 254, 57, 155, 167, 108, 23, 7, 64, 221, 234, 92, 184, 170, 45, 90, 237, 52, 36, 249, 255, 151, 107, 143, 214, 13, 5, 134, 207, 2, 17, 0, 0, 0, 13, 82, 212, 126, 148, 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