Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5648fa04df32afd1ff5e70d6e1fba222f54ed7c4f90fc4e2719d7b0682f0da1

Tx prefix hash: 0e9dbd0296aae28101533ec315ac8d93d1f756f0802f8222cdbcc506d33eb660
Tx public key: c13c5d60d9bb0b5a28ed405554a937f860c2a38d761635bcc1abf54c2cb19235
Timestamp: 1721339397 Timestamp [UCT]: 2024-07-18 21:49:57 Age [y:d:h:m:s]: 01:110:02:28:22
Block: 1068666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337171 RingCT/type: yes/0
Extra: 01c13c5d60d9bb0b5a28ed405554a937f860c2a38d761635bcc1abf54c2cb1923502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc613df41bbc2d5e24e800f75d874c44ffc73d848896a3dee9cda8722451b6ec 0.600000000000 1539787 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": 1068676, "vin": [ { "gen": { "height": 1068666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc613df41bbc2d5e24e800f75d874c44ffc73d848896a3dee9cda8722451b6ec" } } ], "extra": [ 1, 193, 60, 93, 96, 217, 187, 11, 90, 40, 237, 64, 85, 84, 169, 55, 248, 96, 194, 163, 141, 118, 22, 53, 188, 193, 171, 245, 76, 44, 177, 146, 53, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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