Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93b94208bf398523146708e15f330c0e2016d66c1ea3e4af8cc1a048f994fc1e

Tx prefix hash: dd4b330b13bf430637b87dcd1e3032ae4f0bfeed5df94c7fa1c3417a6551a6d6
Tx public key: b7b914fb72b50e9bf21dfc5e0c0018cba65a49e814111cec0bd0464c9c8d157b
Timestamp: 1750742098 Timestamp [UCT]: 2025-06-24 05:14:58 Age [y:d:h:m:s]: 00:149:20:22:34
Block: 1311594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105023 RingCT/type: yes/0
Extra: 01b7b914fb72b50e9bf21dfc5e0c0018cba65a49e814111cec0bd0464c9c8d157b02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2d4f0ed9e9e18dc827a0aefd16f80d448e532a64d8bc58b04f1f09e506d6415 0.600000000000 1799221 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": 1311604, "vin": [ { "gen": { "height": 1311594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2d4f0ed9e9e18dc827a0aefd16f80d448e532a64d8bc58b04f1f09e506d6415" } } ], "extra": [ 1, 183, 185, 20, 251, 114, 181, 14, 155, 242, 29, 252, 94, 12, 0, 24, 203, 166, 90, 73, 232, 20, 17, 28, 236, 11, 208, 70, 76, 156, 141, 21, 123, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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