Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 642d0b53c35c80f7573148fd511cecb5b5ea28ef1472780c0f28d327282c947a

Tx prefix hash: c98b8dcb4f29aca9b5cddd60e70165901ed5379ad46df3b0c40a349f05fa3f98
Tx public key: 94651af3f396e8dde7152e29911958bdc1d7b8d59f57ff513755b5c0c61ec679
Timestamp: 1711173976 Timestamp [UCT]: 2024-03-23 06:06:16 Age [y:d:h:m:s]: 01:014:21:18:40
Block: 984404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271582 RingCT/type: yes/0
Extra: 0194651af3f396e8dde7152e29911958bdc1d7b8d59f57ff513755b5c0c61ec6790211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cab56a1cf9d2e9dd683560d0ee1e6f2ea227a2d3879f90d41de2401a4236c3df 0.600000000000 1444575 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": 984414, "vin": [ { "gen": { "height": 984404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cab56a1cf9d2e9dd683560d0ee1e6f2ea227a2d3879f90d41de2401a4236c3df" } } ], "extra": [ 1, 148, 101, 26, 243, 243, 150, 232, 221, 231, 21, 46, 41, 145, 25, 88, 189, 193, 215, 184, 213, 159, 87, 255, 81, 55, 85, 181, 192, 198, 30, 198, 121, 2, 17, 0, 0, 0, 2, 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