Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0d5e7b53feca9c21cf67d5a2dc8ba3ae49d74769a006cbb1062c22bb49afa5d

Tx prefix hash: ff412f2958a8785befc00d578a7b847950d1b1204c7c0199ecd73ff1966f67e7
Tx public key: 287d505bb634ba7a1aadcaefe5f3cd85fa4d8f59d555a7d394b4654163335338
Timestamp: 1735156342 Timestamp [UCT]: 2024-12-25 19:52:22 Age [y:d:h:m:s]: 00:088:05:32:26
Block: 1183094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62826 RingCT/type: yes/0
Extra: 01287d505bb634ba7a1aadcaefe5f3cd85fa4d8f59d555a7d394b46541633353380211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdb6e784b9886e6a61315721fbaae4f1bc881b2c6a958e7c16ab5b812e65fe94 0.600000000000 1669535 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": 1183104, "vin": [ { "gen": { "height": 1183094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdb6e784b9886e6a61315721fbaae4f1bc881b2c6a958e7c16ab5b812e65fe94" } } ], "extra": [ 1, 40, 125, 80, 91, 182, 52, 186, 122, 26, 173, 202, 239, 229, 243, 205, 133, 250, 77, 143, 89, 213, 85, 167, 211, 148, 180, 101, 65, 99, 51, 83, 56, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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