Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c4f88e0f04cee518630e49d2a9131a9f950f5aa37e0047481d0e62dc54e1234

Tx prefix hash: 353ab7c783ea6049439b1f250e0b7d5dd6d3b43ab31c19d2d0a980ad8f1c3f8c
Tx public key: cae9745445614e5e80471ee2055981a3070fd30260eaf4d1c5555c0dcb54c846
Timestamp: 1697972108 Timestamp [UCT]: 2023-10-22 10:55:08 Age [y:d:h:m:s]: 01:178:05:19:28
Block: 875144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388385 RingCT/type: yes/0
Extra: 01cae9745445614e5e80471ee2055981a3070fd30260eaf4d1c5555c0dcb54c84602110000000175e3f0e9000000000000000000

1 output(s) for total of 0.773187204000 dcy

stealth address amount amount idx
00: cddc7fb70f356eadf87731dcdef73f70bb5e44c44eacd7aec14e7ca067e3d047 0.773187204000 1330388 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": 875154, "vin": [ { "gen": { "height": 875144 } } ], "vout": [ { "amount": 773187204, "target": { "key": "cddc7fb70f356eadf87731dcdef73f70bb5e44c44eacd7aec14e7ca067e3d047" } } ], "extra": [ 1, 202, 233, 116, 84, 69, 97, 78, 94, 128, 71, 30, 226, 5, 89, 129, 163, 7, 15, 211, 2, 96, 234, 244, 209, 197, 85, 92, 13, 203, 84, 200, 70, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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