Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ee8509920c5edbecd5d2b1ae6ba4928bab82b9458a0f7172db4c5191b2ccab8

Tx prefix hash: 7178261d7c672d877df6d9effd81b530a23ecd55e0ea1759acff3e96823b9d1e
Tx public key: aafa07b20a7b43df5e28fb6d11beec191f2e053b58023d33aec141919eefa262
Timestamp: 1721226489 Timestamp [UCT]: 2024-07-17 14:28:09 Age [y:d:h:m:s]: 00:251:14:35:55
Block: 1067738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179713 RingCT/type: yes/0
Extra: 01aafa07b20a7b43df5e28fb6d11beec191f2e053b58023d33aec141919eefa262021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d9e54f1f32bfd5fbd220478e4cbd132179287db99289980af40744c006305c2 0.600000000000 1538633 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": 1067748, "vin": [ { "gen": { "height": 1067738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d9e54f1f32bfd5fbd220478e4cbd132179287db99289980af40744c006305c2" } } ], "extra": [ 1, 170, 250, 7, 178, 10, 123, 67, 223, 94, 40, 251, 109, 17, 190, 236, 25, 31, 46, 5, 59, 88, 2, 61, 51, 174, 193, 65, 145, 158, 239, 162, 98, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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