Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01b58822fa2d177d7efd3028a876250e8ddfc34163df7b70bf3031b68bc3a522

Tx prefix hash: 1499a842c43ab33674bd2039b4dcc712852201a44a9d9ae50688e6671a46fd13
Tx public key: 8656313ca26c83a7a86ea00dcf07ab0e6004f5b7832b067d1a46d8a235a722a9
Timestamp: 1716259736 Timestamp [UCT]: 2024-05-21 02:48:56 Age [y:d:h:m:s]: 00:360:20:34:10
Block: 1026560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257924 RingCT/type: yes/0
Extra: 018656313ca26c83a7a86ea00dcf07ab0e6004f5b7832b067d1a46d8a235a722a90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52fb78a95678297702232eb5974b95ee18c3086075b4f0b7d4ba7dcd84a8036a 0.600000000000 1493707 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": 1026570, "vin": [ { "gen": { "height": 1026560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52fb78a95678297702232eb5974b95ee18c3086075b4f0b7d4ba7dcd84a8036a" } } ], "extra": [ 1, 134, 86, 49, 60, 162, 108, 131, 167, 168, 110, 160, 13, 207, 7, 171, 14, 96, 4, 245, 183, 131, 43, 6, 125, 26, 70, 216, 162, 53, 167, 34, 169, 2, 17, 0, 0, 0, 1, 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