Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66fcb96eb499ec60819ca0387ebc9cd9689a8d741225e6ebf5c7b16a12cc2a82

Tx prefix hash: 607bc443912143c1ebf41d76cb740f9a2d27c3bf2d713cde97151a8d923d9042
Tx public key: ddd78f1e3c4468f887415d245d7bbbf45774ca264a0b28180728fa8c3f75f451
Timestamp: 1678981561 Timestamp [UCT]: 2023-03-16 15:46:01 Age [y:d:h:m:s]: 01:248:02:37:17
Block: 718382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438176 RingCT/type: yes/0
Extra: 01ddd78f1e3c4468f887415d245d7bbbf45774ca264a0b28180728fa8c3f75f4510211000000035029cbac000000000000000000

1 output(s) for total of 2.556831486000 dcy

stealth address amount amount idx
00: f529556ef03c01c3d025a8c54c157b61f5b2456723eb947a89d4cb6345c48763 2.556831486000 1163045 of 0

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": 718392, "vin": [ { "gen": { "height": 718382 } } ], "vout": [ { "amount": 2556831486, "target": { "key": "f529556ef03c01c3d025a8c54c157b61f5b2456723eb947a89d4cb6345c48763" } } ], "extra": [ 1, 221, 215, 143, 30, 60, 68, 104, 248, 135, 65, 93, 36, 93, 123, 187, 244, 87, 116, 202, 38, 74, 11, 40, 24, 7, 40, 250, 140, 63, 117, 244, 81, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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