Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05090f74ade187e863f0f0323d5c871e497fd9b96b12d8b68c043318d322419c

Tx prefix hash: 0496f9fd1d78a6e95b2d49a36fc843601fd8beedd56557ce99c10aa348dc4256
Tx public key: d195f925e3850a20654c83d08bc64897e37dab3cc0dbe513d761f274f1ceb03a
Timestamp: 1736042832 Timestamp [UCT]: 2025-01-05 02:07:12 Age [y:d:h:m:s]: 00:091:15:02:07
Block: 1190430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65251 RingCT/type: yes/0
Extra: 01d195f925e3850a20654c83d08bc64897e37dab3cc0dbe513d761f274f1ceb03a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 429c0b5ad7501d5d2e5c16e80d01b8c50d1b822d51b869ec5bc58326d9749166 0.600000000000 1676947 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": 1190440, "vin": [ { "gen": { "height": 1190430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "429c0b5ad7501d5d2e5c16e80d01b8c50d1b822d51b869ec5bc58326d9749166" } } ], "extra": [ 1, 209, 149, 249, 37, 227, 133, 10, 32, 101, 76, 131, 208, 139, 198, 72, 151, 227, 125, 171, 60, 192, 219, 229, 19, 215, 97, 242, 116, 241, 206, 176, 58, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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