Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5019785c4a7066ec3f215bf44c6481f2637d83a0832ee007e57f6e0442f4e07

Tx prefix hash: 64a7fb2db6bf3c96930ec5fc9332d5e3bc24a066c2d91dbb86da0315dde924be
Tx public key: a89198e3be1371c9813ea8bfc807cd86e7d3257da0c8996b2c12793fbfed0327
Timestamp: 1714978882 Timestamp [UCT]: 2024-05-06 07:01:22 Age [y:d:h:m:s]: 00:333:14:02:02
Block: 1015929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238450 RingCT/type: yes/0
Extra: 01a89198e3be1371c9813ea8bfc807cd86e7d3257da0c8996b2c12793fbfed03270211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37209f3cf776a611b400732ce7f6f05f0a078bf13b8f056572e8130009eefb9e 0.600000000000 1479372 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": 1015939, "vin": [ { "gen": { "height": 1015929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37209f3cf776a611b400732ce7f6f05f0a078bf13b8f056572e8130009eefb9e" } } ], "extra": [ 1, 168, 145, 152, 227, 190, 19, 113, 201, 129, 62, 168, 191, 200, 7, 205, 134, 231, 211, 37, 125, 160, 200, 153, 107, 44, 18, 121, 63, 191, 237, 3, 39, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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