Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f76dd39265aa4000d74f86ff330da1245e25aebfe8655ffe545c2a558e2b1d9

Tx prefix hash: 47e0da3c6bba9748a5d175ec39f6d50d72cbfa0d9a44e1368fa70c3ab1e3b0a9
Tx public key: b5d3f9cc626cf78530faf600af36aa79ce2bd074376410430cf9c5054b217652
Timestamp: 1763634006 Timestamp [UTC]: 2025-11-20 10:20:06 Age [y:d:h:m:s]: 00:361:00:00:13
Block: 1416162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263420 RingCT/type: yes/0
Extra: 01b5d3f9cc626cf78530faf600af36aa79ce2bd074376410430cf9c5054b2176520211000000017b1e51ac000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 14f7b8d7bc4b33fabf4b2c3ec063e44bbb617cba103e9f389ffa81dec6fb9591 0.000600000000 1904681 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": 1416172, "vin": [ { "gen": { "height": 1416162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14f7b8d7bc4b33fabf4b2c3ec063e44bbb617cba103e9f389ffa81dec6fb9591" } } ], "extra": [ 1, 181, 211, 249, 204, 98, 108, 247, 133, 48, 250, 246, 0, 175, 54, 170, 121, 206, 43, 208, 116, 55, 100, 16, 67, 12, 249, 197, 5, 75, 33, 118, 82, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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: