Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6831a0aacabf922c98a06dedd4e8cf1b5b52b13d118183d1a84aed7318de111e

Tx prefix hash: 29f4e1627608f0f834b8e28206887d56d92667069cdf9e9c9278d3ea4c2b6d41
Tx public key: ecc8be86e0dbae7a2566d6122d288a1d8c28bfec3f141cc5f7e60cfe7a7e9894
Timestamp: 1703088021 Timestamp [UCT]: 2023-12-20 16:00:21 Age [y:d:h:m:s]: 01:115:22:02:39
Block: 917360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343966 RingCT/type: yes/0
Extra: 01ecc8be86e0dbae7a2566d6122d288a1d8c28bfec3f141cc5f7e60cfe7a7e9894021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66758590fb07c67d50d132b324da002cbcaf098dd927a66a54290aa29c8804df 0.600000000000 1374934 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": 917370, "vin": [ { "gen": { "height": 917360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66758590fb07c67d50d132b324da002cbcaf098dd927a66a54290aa29c8804df" } } ], "extra": [ 1, 236, 200, 190, 134, 224, 219, 174, 122, 37, 102, 214, 18, 45, 40, 138, 29, 140, 40, 191, 236, 63, 20, 28, 197, 247, 230, 12, 254, 122, 126, 152, 148, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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