Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 866daf402f00121f57e1f56929a5a9a6a4281fcce9353034a325fdb2387590a9

Tx prefix hash: a1a642e24fe963154dfc9445e98e9b7fafb2dec68daf8b8595c33cffbb58bf41
Tx public key: bbf848b8c0ee3871f57c36b5ea22058eb2703e4137c6ebceef57b3f8e32f4300
Timestamp: 1728265405 Timestamp [UCT]: 2024-10-07 01:43:25 Age [y:d:h:m:s]: 01:032:08:11:46
Block: 1126083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281491 RingCT/type: yes/0
Extra: 01bbf848b8c0ee3871f57c36b5ea22058eb2703e4137c6ebceef57b3f8e32f430002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64b8f44665294c9023a52d78cd9b922156c7af7d33d4e1961f123a78a6fd6e50 0.600000000000 1608862 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": 1126093, "vin": [ { "gen": { "height": 1126083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64b8f44665294c9023a52d78cd9b922156c7af7d33d4e1961f123a78a6fd6e50" } } ], "extra": [ 1, 187, 248, 72, 184, 192, 238, 56, 113, 245, 124, 54, 181, 234, 34, 5, 142, 178, 112, 62, 65, 55, 198, 235, 206, 239, 87, 179, 248, 227, 47, 67, 0, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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