Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 542b6dab133f799fa090910b1433f01a9189797adc5a56e82c3d1442f8822130

Tx prefix hash: d54f844f26e2cd2fdef04d690c722bc2a8f02bcb04da6b13b7770ae14c418dd8
Tx public key: 9b7397d9cb7ad214aaadad5792b0b795631b76f539e7f94f78288845ed4aa7dd
Timestamp: 1758175965 Timestamp [UCT]: 2025-09-18 06:12:45 Age [y:d:h:m:s]: 00:112:15:00:15
Block: 1370943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80646 RingCT/type: yes/0
Extra: 019b7397d9cb7ad214aaadad5792b0b795631b76f539e7f94f78288845ed4aa7dd021100000009b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17efa2bd8b61047e4d6a1d6a2239d055fc68be2cc3c0b2e47d8e81bfc38107bc 0.600000000000 1859020 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": 1370953, "vin": [ { "gen": { "height": 1370943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17efa2bd8b61047e4d6a1d6a2239d055fc68be2cc3c0b2e47d8e81bfc38107bc" } } ], "extra": [ 1, 155, 115, 151, 217, 203, 122, 210, 20, 170, 173, 173, 87, 146, 176, 183, 149, 99, 27, 118, 245, 57, 231, 249, 79, 120, 40, 136, 69, 237, 74, 167, 221, 2, 17, 0, 0, 0, 9, 178, 247, 132, 196, 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