Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51b0f22fa9d4f5fc60af31baa135f3e1ccc60b218fdb820669a71e7c2170b0b0

Tx prefix hash: e56e647f36ac9673bfc91bdf823358591730dc6082b01216ec7d86768f453a4a
Tx public key: e7ffc0ebb901753de99ec17dc118e0d20a1ea9242a6cb4c86ced0796749b5379
Timestamp: 1709998758 Timestamp [UCT]: 2024-03-09 15:39:18 Age [y:d:h:m:s]: 00:352:14:55:38
Block: 974642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252107 RingCT/type: yes/0
Extra: 01e7ffc0ebb901753de99ec17dc118e0d20a1ea9242a6cb4c86ced0796749b537902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 516c7df385667f7721bb3d85daa2ba8293eb386ea99c5b224abf0357c455d4f9 0.600000000000 1434601 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": 974652, "vin": [ { "gen": { "height": 974642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "516c7df385667f7721bb3d85daa2ba8293eb386ea99c5b224abf0357c455d4f9" } } ], "extra": [ 1, 231, 255, 192, 235, 185, 1, 117, 61, 233, 158, 193, 125, 193, 24, 224, 210, 10, 30, 169, 36, 42, 108, 180, 200, 108, 237, 7, 150, 116, 155, 83, 121, 2, 17, 0, 0, 0, 3, 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