Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a254d592152d3d95864ab97f5ffb8de14e6fe524d4879090cfd6a40e514bd65

Tx prefix hash: fa54d22c094c069022aac8d821caaddba1202a4cdbe6f7b4ac33a2640dcd369f
Tx public key: d188b6d8e6109f44f80ac246edf82c597912fd8a8883356a6f4b3947cc88a23f
Timestamp: 1737663464 Timestamp [UCT]: 2025-01-23 20:17:44 Age [y:d:h:m:s]: 00:144:20:05:59
Block: 1203791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103271 RingCT/type: yes/0
Extra: 01d188b6d8e6109f44f80ac246edf82c597912fd8a8883356a6f4b3947cc88a23f021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a3d7a8153b70e39cfb538c20d15fcfd762a52b6854c88d7ba73ad70997a4413 0.600000000000 1690470 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": 1203801, "vin": [ { "gen": { "height": 1203791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a3d7a8153b70e39cfb538c20d15fcfd762a52b6854c88d7ba73ad70997a4413" } } ], "extra": [ 1, 209, 136, 182, 216, 230, 16, 159, 68, 248, 10, 194, 70, 237, 248, 44, 89, 121, 18, 253, 138, 136, 131, 53, 106, 111, 75, 57, 71, 204, 136, 162, 63, 2, 17, 0, 0, 0, 8, 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