Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c96d1a4e91095bd50794f7d6a1a3ee6426a0051ad36b6655c1f9e043947328bf

Tx prefix hash: 03a0f405200935e46239a544ab9cdaec98435446263696298ebad1969a1d4947
Tx public key: 6487bf0a2a0bc2e6a1a2abb1bcec2b4c95a48c529fde669d71a5000838499f68
Timestamp: 1703036995 Timestamp [UCT]: 2023-12-20 01:49:55 Age [y:d:h:m:s]: 01:336:00:26:31
Block: 916923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499014 RingCT/type: yes/0
Extra: 016487bf0a2a0bc2e6a1a2abb1bcec2b4c95a48c529fde669d71a5000838499f68021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2edf3f22d3f0ad95cfab1ac73f557703418e94dd9823fdc54cb6f5f82f3f2c1a 0.600000000000 1374485 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": 916933, "vin": [ { "gen": { "height": 916923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2edf3f22d3f0ad95cfab1ac73f557703418e94dd9823fdc54cb6f5f82f3f2c1a" } } ], "extra": [ 1, 100, 135, 191, 10, 42, 11, 194, 230, 161, 162, 171, 177, 188, 236, 43, 76, 149, 164, 140, 82, 159, 222, 102, 157, 113, 165, 0, 8, 56, 73, 159, 104, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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