Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baa19d6fa788cf5a3e9bdc7093179e04b07f2fe91271511c9970dc3e493f4fc2

Tx prefix hash: 244095bfe7088f23b85827e65543f25f9316381bf01bb13c2fecb84c1da27065
Tx public key: 2cf26c1ee7fa93fce7086f0b40d1be8e961a6c3c5698e3526b6890addb6f7896
Timestamp: 1720433528 Timestamp [UCT]: 2024-07-08 10:12:08 Age [y:d:h:m:s]: 00:342:23:29:33
Block: 1061157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244993 RingCT/type: yes/0
Extra: 012cf26c1ee7fa93fce7086f0b40d1be8e961a6c3c5698e3526b6890addb6f7896021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acc4af434fde7100a94f07f68baa807f70997f1a502cfe238b153365e2c9e2be 0.600000000000 1531648 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": 1061167, "vin": [ { "gen": { "height": 1061157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acc4af434fde7100a94f07f68baa807f70997f1a502cfe238b153365e2c9e2be" } } ], "extra": [ 1, 44, 242, 108, 30, 231, 250, 147, 252, 231, 8, 111, 11, 64, 209, 190, 142, 150, 26, 108, 60, 86, 152, 227, 82, 107, 104, 144, 173, 219, 111, 120, 150, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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