Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bcaf9e0ee02135e7978e3e3d15ef7b7d8ce3802c1361761746ddaf5d08cd492

Tx prefix hash: 2128887e8dbd7345f5440827c9d08b19d6b203b428f543cee2f91d3a1504cae0
Tx public key: 1f0d19596f7044c45861f1894a404e4f134cb9aaddef83d263c425724671704d
Timestamp: 1716104871 Timestamp [UCT]: 2024-05-19 07:47:51 Age [y:d:h:m:s]: 00:360:15:21:56
Block: 1025270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257794 RingCT/type: yes/0
Extra: 011f0d19596f7044c45861f1894a404e4f134cb9aaddef83d263c425724671704d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1a8da37efb47a0c7e594d8b5cccc4a8971667e403806e33d365f818e405851b 0.600000000000 1491653 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": 1025280, "vin": [ { "gen": { "height": 1025270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1a8da37efb47a0c7e594d8b5cccc4a8971667e403806e33d365f818e405851b" } } ], "extra": [ 1, 31, 13, 25, 89, 111, 112, 68, 196, 88, 97, 241, 137, 74, 64, 78, 79, 19, 76, 185, 170, 221, 239, 131, 210, 99, 196, 37, 114, 70, 113, 112, 77, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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