Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08ccb4682092876f7b03a413d21c4d2e0a96bfaa3f8da69f0c5fb49830078a85

Tx prefix hash: 751128470fd271a58718b7c28e0cf96afdd5f706290f434f9d638818eeff0fa2
Tx public key: a3cf2eb1bd4260f6e5f43bd924add7e82ce664dda27af34d9dc0c389e55e374e
Timestamp: 1688797784 Timestamp [UCT]: 2023-07-08 06:29:44 Age [y:d:h:m:s]: 01:309:11:03:11
Block: 799144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482308 RingCT/type: yes/0
Extra: 01a3cf2eb1bd4260f6e5f43bd924add7e82ce664dda27af34d9dc0c389e55e374e02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.380715876000 dcy

stealth address amount amount idx
00: 34b140737b110915239569ebd0855d4f97fd8608d8fa95a50057a37505f57ccf 1.380715876000 1250127 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": 799154, "vin": [ { "gen": { "height": 799144 } } ], "vout": [ { "amount": 1380715876, "target": { "key": "34b140737b110915239569ebd0855d4f97fd8608d8fa95a50057a37505f57ccf" } } ], "extra": [ 1, 163, 207, 46, 177, 189, 66, 96, 246, 229, 244, 59, 217, 36, 173, 215, 232, 44, 230, 100, 221, 162, 122, 243, 77, 157, 192, 195, 137, 229, 94, 55, 78, 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