Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a82c5eb9f9b2aaa9db9b359bf4f62d1c6eaddb2d9b26d4a2c3577eab1cdf9691

Tx prefix hash: f79fe2f1119fd67030e5d464e209c8ee627115d33ab45c023729803a81358336
Tx public key: 6cff413447da0626b97250afc9ae91730c92100a3c259eec265f0489882910e7
Timestamp: 1723919009 Timestamp [UCT]: 2024-08-17 18:23:29 Age [y:d:h:m:s]: 00:259:09:03:07
Block: 1090054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185257 RingCT/type: yes/0
Extra: 016cff413447da0626b97250afc9ae91730c92100a3c259eec265f0489882910e702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c85bcd73ac1e55111eb73c5a4452697f1291c6bb2e4d55c0c3c8df90cfd16fe 0.600000000000 1564677 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": 1090064, "vin": [ { "gen": { "height": 1090054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c85bcd73ac1e55111eb73c5a4452697f1291c6bb2e4d55c0c3c8df90cfd16fe" } } ], "extra": [ 1, 108, 255, 65, 52, 71, 218, 6, 38, 185, 114, 80, 175, 201, 174, 145, 115, 12, 146, 16, 10, 60, 37, 158, 236, 38, 95, 4, 137, 136, 41, 16, 231, 2, 17, 0, 0, 0, 1, 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