Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7565cf5e3603134bc1ec5e9d27343127110a1246f8793f8e534a787ec5f5c5ab

Tx prefix hash: 201c543a16e137a4b85b4f662fced06b7819d3f67de684b000b980d8b3ba6aa2
Tx public key: a70e34109a6bf6df27d6bf351c6df0984ef1aaeca5164b1d6ef495898be4cc62
Timestamp: 1711087780 Timestamp [UCT]: 2024-03-22 06:09:40 Age [y:d:h:m:s]: 01:071:08:46:20
Block: 983696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312006 RingCT/type: yes/0
Extra: 01a70e34109a6bf6df27d6bf351c6df0984ef1aaeca5164b1d6ef495898be4cc6202110000000f0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a6555a9f157de6bab030ecd2df90e0900fa2d216aa1df3d5d6cd06cff1a416f 0.600000000000 1443837 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": 983706, "vin": [ { "gen": { "height": 983696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a6555a9f157de6bab030ecd2df90e0900fa2d216aa1df3d5d6cd06cff1a416f" } } ], "extra": [ 1, 167, 14, 52, 16, 154, 107, 246, 223, 39, 214, 191, 53, 28, 109, 240, 152, 78, 241, 170, 236, 165, 22, 75, 29, 110, 244, 149, 137, 139, 228, 204, 98, 2, 17, 0, 0, 0, 15, 0, 17, 5, 91, 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