Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5e92b9803630e5580b953cb5c49d29ea8dc10d4d50ba98c70da9e56ec646a69

Tx prefix hash: 1e035e59b77bb64db93f3f3773528dc9413fad9ef9d9431d7c7b5a6f7e05f8e3
Tx public key: f3caf1565b09b92e50d38e2fa66610b5f8c4d799fea1022fb96dae03cbf7bce3
Timestamp: 1711407139 Timestamp [UCT]: 2024-03-25 22:52:19 Age [y:d:h:m:s]: 01:065:04:49:49
Block: 986337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307591 RingCT/type: yes/0
Extra: 01f3caf1565b09b92e50d38e2fa66610b5f8c4d799fea1022fb96dae03cbf7bce302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee70eebb4edc76260277eec31d2ae6ae9bb6e54fd140197b6f4701cc15ea29e4 0.600000000000 1446566 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": 986347, "vin": [ { "gen": { "height": 986337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee70eebb4edc76260277eec31d2ae6ae9bb6e54fd140197b6f4701cc15ea29e4" } } ], "extra": [ 1, 243, 202, 241, 86, 91, 9, 185, 46, 80, 211, 142, 47, 166, 102, 16, 181, 248, 196, 215, 153, 254, 161, 2, 47, 185, 109, 174, 3, 203, 247, 188, 227, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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