Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1666f060ec461ac74bef48fe51c2b4d5352f62657c191a7a55d06a588e3b6e31

Tx prefix hash: de8248f352399e1ccacb5351c7352aa567bb1ff08e1c7cc06229d53b1f38c48e
Tx public key: 54e7bd4718fdd4ab7226c2914b7bcd50b4a9608fc81bbf7c6efaca15080d6dd5
Timestamp: 1737909632 Timestamp [UCT]: 2025-01-26 16:40:32 Age [y:d:h:m:s]: 00:141:13:30:59
Block: 1205843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100919 RingCT/type: yes/0
Extra: 0154e7bd4718fdd4ab7226c2914b7bcd50b4a9608fc81bbf7c6efaca15080d6dd5021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e8de6291726b4a5698423d55d50e6016921f1a183a53241edc5fee5923068e8 0.600000000000 1692542 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": 1205853, "vin": [ { "gen": { "height": 1205843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e8de6291726b4a5698423d55d50e6016921f1a183a53241edc5fee5923068e8" } } ], "extra": [ 1, 84, 231, 189, 71, 24, 253, 212, 171, 114, 38, 194, 145, 75, 123, 205, 80, 180, 169, 96, 143, 200, 27, 191, 124, 110, 250, 202, 21, 8, 13, 109, 213, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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