Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51635c4b15823eec9f1c03e488835b2118087c7d4c035173789cc04d392d3569

Tx prefix hash: 1afd36e402aed0744cd200d5e1734b4cbee867162f3236d0e5d91db3a61f8e7f
Tx public key: 4286279b24b6ab5ca1b95f9058a5ce5d2974c7ef602aec7b140cce25889e3de4
Timestamp: 1735706935 Timestamp [UCT]: 2025-01-01 04:48:55 Age [y:d:h:m:s]: 00:095:09:00:01
Block: 1187642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67938 RingCT/type: yes/0
Extra: 014286279b24b6ab5ca1b95f9058a5ce5d2974c7ef602aec7b140cce25889e3de4021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1b6786b1a35ebf970450cc82617f73a87311e9f87f0348fabd20c8bcfb8fa7b 0.600000000000 1674135 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": 1187652, "vin": [ { "gen": { "height": 1187642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b6786b1a35ebf970450cc82617f73a87311e9f87f0348fabd20c8bcfb8fa7b" } } ], "extra": [ 1, 66, 134, 39, 155, 36, 182, 171, 92, 161, 185, 95, 144, 88, 165, 206, 93, 41, 116, 199, 239, 96, 42, 236, 123, 20, 12, 206, 37, 136, 158, 61, 228, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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