Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 979247c64de42abeda26a828d844886c29dbe0ad72fb26d0a193a5429faff4f0

Tx prefix hash: 419de52032873a32553e45e9bceb4761420c02cb5d556209a556f848b69ca77a
Tx public key: af3889ec6f9f9ed6c495128fb894db3bd0e6682e55fb99a822291b5b71a49abe
Timestamp: 1626595126 Timestamp [UCT]: 2021-07-18 07:58:46 Age [y:d:h:m:s]: 03:284:03:41:24
Block: 296110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 974449 RingCT/type: yes/0
Extra: 01af3889ec6f9f9ed6c495128fb894db3bd0e6682e55fb99a822291b5b71a49abe021100000012c97064b9000000000000000000

1 output(s) for total of 64.101050235000 dcy

stealth address amount amount idx
00: 44ce2edb29e986f8c0fcc6a4a0f39fe564b9d159a4b1b54559c68a65a5515d15 64.101050235000 619952 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": 296120, "vin": [ { "gen": { "height": 296110 } } ], "vout": [ { "amount": 64101050235, "target": { "key": "44ce2edb29e986f8c0fcc6a4a0f39fe564b9d159a4b1b54559c68a65a5515d15" } } ], "extra": [ 1, 175, 56, 137, 236, 111, 159, 158, 214, 196, 149, 18, 143, 184, 148, 219, 59, 208, 230, 104, 46, 85, 251, 153, 168, 34, 41, 27, 91, 113, 164, 154, 190, 2, 17, 0, 0, 0, 18, 201, 112, 100, 185, 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