Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0845f25e946007b2b399f4db3e53ff1f039e0b89170fefd48067e37c5bb170c0

Tx prefix hash: f80c1454e92d0287b7059e2f219869f5b8eca103ab3c65e7648b5dfb83787757
Tx public key: da1a99790a6f1bf61f050676303edcf51564287ed13a340a446bd1fd92d32f97
Timestamp: 1767107204 Timestamp [UTC]: 2025-12-30 15:06:44 Age [y:d:h:m:s]: 00:326:09:00:54
Block: 1444957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238537 RingCT/type: yes/0
Extra: 01da1a99790a6f1bf61f050676303edcf51564287ed13a340a446bd1fd92d32f9702110000001049d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ef6ab5d3fd2b36bc01c7b5d747af063b5f7c7210af52bdbaf2ae789db5b9230c 0.000600000000 1933895 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": 1444967, "vin": [ { "gen": { "height": 1444957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef6ab5d3fd2b36bc01c7b5d747af063b5f7c7210af52bdbaf2ae789db5b9230c" } } ], "extra": [ 1, 218, 26, 153, 121, 10, 111, 27, 246, 31, 5, 6, 118, 48, 62, 220, 245, 21, 100, 40, 126, 209, 58, 52, 10, 68, 107, 209, 253, 146, 211, 47, 151, 2, 17, 0, 0, 0, 16, 73, 215, 62, 152, 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: