Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e55957bb0590cda59e2b1f2fc2a63ff6aaf40503474a10030562e898c0d435a

Tx prefix hash: 6b99638f0283a8ba0d574e1a11d424be0a0939eb37578f2dfd02fd004d19c90c
Tx public key: dda3e36098951a09c9295c79c12fc905a533fa6df8f87b59d58e716880427c7b
Timestamp: 1761213941 Timestamp [UTC]: 2025-10-23 10:05:41 Age [y:d:h:m:s]: 01:023:11:28:59
Block: 1396126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283049 RingCT/type: yes/0
Extra: 01dda3e36098951a09c9295c79c12fc905a533fa6df8f87b59d58e716880427c7b02110000000201491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 64f78f7f0c03b7e59e96e07d141afbec08c16db4603bfb6d4f1dc121bac083a2 0.000600000000 1884411 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": 1396136, "vin": [ { "gen": { "height": 1396126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64f78f7f0c03b7e59e96e07d141afbec08c16db4603bfb6d4f1dc121bac083a2" } } ], "extra": [ 1, 221, 163, 227, 96, 152, 149, 26, 9, 201, 41, 92, 121, 193, 47, 201, 5, 165, 51, 250, 109, 248, 248, 123, 89, 213, 142, 113, 104, 128, 66, 124, 123, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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: