Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0444ff42f52adf3ef02a657add4a23a9a58fa7655c695a9fa4b8c4c30a4f87e9

Tx prefix hash: 90b45013fdf11b52176d36b1de426db59e3a906362147550766ffd44d79b440f
Tx public key: 45eb09160c6b1a2203ba255414c5d2ecaf18cda7b889737444ad0a509e0cf961
Timestamp: 1769714671 Timestamp [UTC]: 2026-01-29 19:24:31 Age [y:d:h:m:s]: 00:105:03:48:00
Block: 1466387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67557 RingCT/type: yes/0
Extra: 0145eb09160c6b1a2203ba255414c5d2ecaf18cda7b889737444ad0a509e0cf961021100000001215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5512d22c56b2a4dd30dbab0d183d50cb28085a464b401b6ecfc44f1ba99b1160 0.000600000000 1955623 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": 1466397, "vin": [ { "gen": { "height": 1466387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5512d22c56b2a4dd30dbab0d183d50cb28085a464b401b6ecfc44f1ba99b1160" } } ], "extra": [ 1, 69, 235, 9, 22, 12, 107, 26, 34, 3, 186, 37, 84, 20, 197, 210, 236, 175, 24, 205, 167, 184, 137, 115, 116, 68, 173, 10, 80, 158, 12, 249, 97, 2, 17, 0, 0, 0, 1, 33, 91, 191, 137, 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: