Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 673202d13e56d9f62f46a3a84a8c83f1d47ca7f19d0ec83f90e50eb64346a03a

Tx prefix hash: 7209c0db3f31a930d2a4bfe578a73ddfa7b732929f07c16840b7d0a4d54623b4
Tx public key: 10c49bdf0752d7ae5c720d02e915b15a51b3dcfaa243ccf04d002cb052bf9706
Timestamp: 1709916353 Timestamp [UCT]: 2024-03-08 16:45:53 Age [y:d:h:m:s]: 01:244:17:18:20
Block: 973964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433616 RingCT/type: yes/0
Extra: 0110c49bdf0752d7ae5c720d02e915b15a51b3dcfaa243ccf04d002cb052bf97060211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 117f0d9078031bb71a44eb8a7d1ca0ab3484de52415a94319f6d6baa70134eaa 0.600000000000 1433907 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": 973974, "vin": [ { "gen": { "height": 973964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "117f0d9078031bb71a44eb8a7d1ca0ab3484de52415a94319f6d6baa70134eaa" } } ], "extra": [ 1, 16, 196, 155, 223, 7, 82, 215, 174, 92, 114, 13, 2, 233, 21, 177, 90, 81, 179, 220, 250, 162, 67, 204, 240, 77, 0, 44, 176, 82, 191, 151, 6, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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