Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25110198ff7426be2d16e63610eb7f21a6bac0d1c76291e073f8f3484dab5610

Tx prefix hash: 41c84d5a9cf6b4cbf3026cda396b5cfcaf73ae626a25392f6277411958ed1949
Tx public key: 0104c1eaca1ff3fd0e592f24d49b7bcadc0ebde90195d9b4b6e313017a3cd60a
Timestamp: 1759404179 Timestamp [UCT]: 2025-10-02 11:22:59 Age [y:d:h:m:s]: 00:007:01:24:48
Block: 1381122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5047 RingCT/type: yes/0
Extra: 010104c1eaca1ff3fd0e592f24d49b7bcadc0ebde90195d9b4b6e313017a3cd60a021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37d1206d5bc2f5c5893f8a9348f3e357d2adefff703bfdb01eae503000da20a4 0.600000000000 1869237 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": 1381132, "vin": [ { "gen": { "height": 1381122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37d1206d5bc2f5c5893f8a9348f3e357d2adefff703bfdb01eae503000da20a4" } } ], "extra": [ 1, 1, 4, 193, 234, 202, 31, 243, 253, 14, 89, 47, 36, 212, 155, 123, 202, 220, 14, 189, 233, 1, 149, 217, 180, 182, 227, 19, 1, 122, 60, 214, 10, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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