Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d47853e54cc3b7fab69a62e2c65e07217ed6308a6db46ec23cd60c125c16eb3

Tx prefix hash: 9c63050868d58db88f9094c403be8c9794812cb10a3b91e93be78daf44b61338
Tx public key: aad8c2c0e30f06fe6392b99a1cb3fc3b91c6324f18e5f497f13264ebfd0bea37
Timestamp: 1711986162 Timestamp [UCT]: 2024-04-01 15:42:42 Age [y:d:h:m:s]: 01:022:19:43:07
Block: 991079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277325 RingCT/type: yes/0
Extra: 01aad8c2c0e30f06fe6392b99a1cb3fc3b91c6324f18e5f497f13264ebfd0bea3702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edbbdf488f04012bfd2d1a19b7c57f0f333654dc21c63f4632e817908ad558ef 0.600000000000 1451413 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": 991089, "vin": [ { "gen": { "height": 991079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edbbdf488f04012bfd2d1a19b7c57f0f333654dc21c63f4632e817908ad558ef" } } ], "extra": [ 1, 170, 216, 194, 192, 227, 15, 6, 254, 99, 146, 185, 154, 28, 179, 252, 59, 145, 198, 50, 79, 24, 229, 244, 151, 241, 50, 100, 235, 253, 11, 234, 55, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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