Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be4ba42774473ccde145bb03130aa5dc30a65efe74f1e93dd24cd9dd8531388d

Tx prefix hash: 97957d1a0830c2954729df0e33723e15f085e41e76b19b8e9a1a79e47dd191f7
Tx public key: 09536511c329826a8ebcc7dd20ed6302d88546cd898a9706414f711389ffcdd4
Timestamp: 1743930060 Timestamp [UTC]: 2025-04-06 09:01:00 Age [y:d:h:m:s]: 01:227:12:21:26
Block: 1255449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426716 RingCT/type: yes/0
Extra: 0109536511c329826a8ebcc7dd20ed6302d88546cd898a9706414f711389ffcdd402110000000adbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4668d712cb99c6d299382b540d1ae9312191f3b3886e1e35efc9b5a6be9c8c48 0.000600000000 1742554 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 dinastycoin-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": 1255459, "vin": [ { "gen": { "height": 1255449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4668d712cb99c6d299382b540d1ae9312191f3b3886e1e35efc9b5a6be9c8c48" } } ], "extra": [ 1, 9, 83, 101, 17, 195, 41, 130, 106, 142, 188, 199, 221, 32, 237, 99, 2, 216, 133, 70, 205, 137, 138, 151, 6, 65, 79, 113, 19, 137, 255, 205, 212, 2, 17, 0, 0, 0, 10, 219, 181, 113, 193, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: