Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 462ee672f72c74a9bcb299f1bd0c4427c1ee5cfba8e5e768e2704f886f00942e

Tx prefix hash: a26535e346fb57eea739b90c274068ea8f09e593b426819c8d60fee545e01c88
Tx public key: 5df3af2e35a2d08cdf9f0112412c074160576e14eecef8ee7507bba43c89ef64
Timestamp: 1723349485 Timestamp [UCT]: 2024-08-11 04:11:25 Age [y:d:h:m:s]: 00:239:23:14:20
Block: 1085324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171375 RingCT/type: yes/0
Extra: 015df3af2e35a2d08cdf9f0112412c074160576e14eecef8ee7507bba43c89ef64021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 855baea0a3c98d34d26eb5f514bbd3a9fbbaa86e67f7fd50554ede6d7e59235e 0.600000000000 1559885 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": 1085334, "vin": [ { "gen": { "height": 1085324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "855baea0a3c98d34d26eb5f514bbd3a9fbbaa86e67f7fd50554ede6d7e59235e" } } ], "extra": [ 1, 93, 243, 175, 46, 53, 162, 208, 140, 223, 159, 1, 18, 65, 44, 7, 65, 96, 87, 110, 20, 238, 206, 248, 238, 117, 7, 187, 164, 60, 137, 239, 100, 2, 17, 0, 0, 0, 7, 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