Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 821d4b4751c1622ebe622637d5e136b23c4e14b0fdd34da9062776e43fd82bb8

Tx prefix hash: fd3f0d552f584fd047ea0cf554f26210e14b8f336bb000994ab18c5b804aa96d
Tx public key: 5962012ecee522f7357dee1448676f4ea396e0335639dea5b32e392a6c09ba93
Timestamp: 1704561363 Timestamp [UCT]: 2024-01-06 17:16:03 Age [y:d:h:m:s]: 01:051:06:14:16
Block: 929550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297713 RingCT/type: yes/0
Extra: 015962012ecee522f7357dee1448676f4ea396e0335639dea5b32e392a6c09ba9302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a5b202816f1e1c3bf229509cd4e98301cc6e70bcb4c7b5e07661e97f4c888c3 0.600000000000 1387426 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": 929560, "vin": [ { "gen": { "height": 929550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a5b202816f1e1c3bf229509cd4e98301cc6e70bcb4c7b5e07661e97f4c888c3" } } ], "extra": [ 1, 89, 98, 1, 46, 206, 229, 34, 247, 53, 125, 238, 20, 72, 103, 111, 78, 163, 150, 224, 51, 86, 57, 222, 165, 179, 46, 57, 42, 108, 9, 186, 147, 2, 17, 0, 0, 0, 4, 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