Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff996f4102745332b94b360325bca947b3701dd4d660457d727a1082d83b5a79

Tx prefix hash: bcb3a8fe9beb783f47286dae2c94ec6168c5c221f4304eb1d5ea13bb64f05d6e
Tx public key: 22baa18458bec45f1b8fe15440ff0e40f96c8864e122fdd274cc89d2be179e7d
Timestamp: 1579040231 Timestamp [UCT]: 2020-01-14 22:17:11 Age [y:d:h:m:s]: 04:350:11:57:41
Block: 45638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140014 RingCT/type: yes/0
Extra: 0122baa18458bec45f1b8fe15440ff0e40f96c8864e122fdd274cc89d2be179e7d0211000000058a2ee0d9000000000000000000

1 output(s) for total of 433.294523707000 dcy

stealth address amount amount idx
00: 43f96fa4cbec70cd84c074d9ebf6d52c594cce37bdf1e1f22214dee5452283ae 433.294523707000 83494 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": 45648, "vin": [ { "gen": { "height": 45638 } } ], "vout": [ { "amount": 433294523707, "target": { "key": "43f96fa4cbec70cd84c074d9ebf6d52c594cce37bdf1e1f22214dee5452283ae" } } ], "extra": [ 1, 34, 186, 161, 132, 88, 190, 196, 95, 27, 143, 225, 84, 64, 255, 14, 64, 249, 108, 136, 100, 225, 34, 253, 210, 116, 204, 137, 210, 190, 23, 158, 125, 2, 17, 0, 0, 0, 5, 138, 46, 224, 217, 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