Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 322f5865beb124803ea6177db96f65ecc311b4b5ac40666e9773ded8d525eac1

Tx prefix hash: bc1a907342ab7e2323ef0de4da2076461e5142e6844dc0ad68d37821785d961b
Tx public key: e40f1eddaefe51341bf1730f616d4d2098cb1859c4d1d3ea15943be6193d374a
Timestamp: 1671999053 Timestamp [UCT]: 2022-12-25 20:10:53 Age [y:d:h:m:s]: 02:027:14:28:30
Block: 660484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541596 RingCT/type: yes/0
Extra: 01e40f1eddaefe51341bf1730f616d4d2098cb1859c4d1d3ea15943be6193d374a021100000002e7ace25d000000000000000000

1 output(s) for total of 3.976878284000 dcy

stealth address amount amount idx
00: e9c28b510bca6e00b812b67705bd157b03e85377c8574683431722b25d64f448 3.976878284000 1101217 of 0

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": 660494, "vin": [ { "gen": { "height": 660484 } } ], "vout": [ { "amount": 3976878284, "target": { "key": "e9c28b510bca6e00b812b67705bd157b03e85377c8574683431722b25d64f448" } } ], "extra": [ 1, 228, 15, 30, 221, 174, 254, 81, 52, 27, 241, 115, 15, 97, 109, 77, 32, 152, 203, 24, 89, 196, 209, 211, 234, 21, 148, 59, 230, 25, 61, 55, 74, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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