Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daa9042b5622e5baff9d6f43d22c2a4ae5e9c7c3d48a835285bde99a9456013b

Tx prefix hash: aea25ff81fe483d34fb18894b69743ca3f9b033258b45791f5062af2b82c9ee5
Tx public key: 9417a65387cdd99936599618a4e0a2a6ef2a5326f2153dd7c9507f6c10151dd6
Timestamp: 1732852761 Timestamp [UCT]: 2024-11-29 03:59:21 Age [y:d:h:m:s]: 00:151:14:20:01
Block: 1164013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108177 RingCT/type: yes/0
Extra: 019417a65387cdd99936599618a4e0a2a6ef2a5326f2153dd7c9507f6c10151dd60211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35f88b252b783e918ae28db6e460211edafc80bc80401f9ce9e0e79362c3fc6d 0.600000000000 1649684 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": 1164023, "vin": [ { "gen": { "height": 1164013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35f88b252b783e918ae28db6e460211edafc80bc80401f9ce9e0e79362c3fc6d" } } ], "extra": [ 1, 148, 23, 166, 83, 135, 205, 217, 153, 54, 89, 150, 24, 164, 224, 162, 166, 239, 42, 83, 38, 242, 21, 61, 215, 201, 80, 127, 108, 16, 21, 29, 214, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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