Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a42e73f0c9f8d9e5d6a7a4593eeb8d076f0148cf5f71116b30e4748adf99da71

Tx prefix hash: 208b77b042ccdfb612b8626c04523ee119f4babc098f9df7e4086cec6fe63b42
Tx public key: 36edeaf083b7bcc994516591ca195c10c2e999cf710d5859c419d282b299c716
Timestamp: 1737476854 Timestamp [UCT]: 2025-01-21 16:27:34 Age [y:d:h:m:s]: 00:330:05:27:10
Block: 1202252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233600 RingCT/type: yes/0
Extra: 0136edeaf083b7bcc994516591ca195c10c2e999cf710d5859c419d282b299c716021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ea28119b32dc8ec18ac556ff14f606d2a16d528aeb56a14830a106713fc27b4 0.600000000000 1688915 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": 1202262, "vin": [ { "gen": { "height": 1202252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ea28119b32dc8ec18ac556ff14f606d2a16d528aeb56a14830a106713fc27b4" } } ], "extra": [ 1, 54, 237, 234, 240, 131, 183, 188, 201, 148, 81, 101, 145, 202, 25, 92, 16, 194, 233, 153, 207, 113, 13, 88, 89, 196, 25, 210, 130, 178, 153, 199, 22, 2, 17, 0, 0, 0, 2, 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