Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baa7afea759c0dfdac17e140d974b4833d9ca684d7502086e0de78aa8d2fe95a

Tx prefix hash: 44bad91cb438bcf01fc2176c84db1d34a35840b17bc50534e9a7fa2434f91a07
Tx public key: cbd949c0dcc9e01771546ae48a558aa6c8b0228c01428d7a049cb6680d33d8a7
Timestamp: 1732029261 Timestamp [UCT]: 2024-11-19 15:14:21 Age [y:d:h:m:s]: 00:139:15:15:30
Block: 1157192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99602 RingCT/type: yes/0
Extra: 01cbd949c0dcc9e01771546ae48a558aa6c8b0228c01428d7a049cb6680d33d8a70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72323e20839a3e3cd518d96107c34769d10a7d758e85ba201b5019937cf0cd43 0.600000000000 1642815 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": 1157202, "vin": [ { "gen": { "height": 1157192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72323e20839a3e3cd518d96107c34769d10a7d758e85ba201b5019937cf0cd43" } } ], "extra": [ 1, 203, 217, 73, 192, 220, 201, 224, 23, 113, 84, 106, 228, 138, 85, 138, 166, 200, 176, 34, 140, 1, 66, 141, 122, 4, 156, 182, 104, 13, 51, 216, 167, 2, 17, 0, 0, 0, 2, 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