Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68a68afa7f260810651223628ef5d712de47707e0d6406993403640dcfb9663d

Tx prefix hash: 774ce6ce9fa499bf47d89c92b3747f8994a2ffc71e8842f03f03441a7df9a9c1
Tx public key: cf19f5be752f737e6cc8ab2f7011f8d13196f13df15ce2a7f16947a26e1a8519
Timestamp: 1685569470 Timestamp [UCT]: 2023-05-31 21:44:30 Age [y:d:h:m:s]: 02:175:18:47:37
Block: 772360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645424 RingCT/type: yes/0
Extra: 01cf19f5be752f737e6cc8ab2f7011f8d13196f13df15ce2a7f16947a26e1a851902110000000475e3f0e9000000000000000000

1 output(s) for total of 1.693756085000 dcy

stealth address amount amount idx
00: d1245a9f7a1fe03b4464f0f8973baaa0d88c3b8fc490d0fad1a85c3e38c073de 1.693756085000 1221761 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": 772370, "vin": [ { "gen": { "height": 772360 } } ], "vout": [ { "amount": 1693756085, "target": { "key": "d1245a9f7a1fe03b4464f0f8973baaa0d88c3b8fc490d0fad1a85c3e38c073de" } } ], "extra": [ 1, 207, 25, 245, 190, 117, 47, 115, 126, 108, 200, 171, 47, 112, 17, 248, 209, 49, 150, 241, 61, 241, 92, 226, 167, 241, 105, 71, 162, 110, 26, 133, 25, 2, 17, 0, 0, 0, 4, 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