Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1695669d6a0e9ac7115eae511c8b9aef627c3761d58a0824f00d846a9cc2cd9

Tx prefix hash: bf684a629de1b055a65ba5dd8b1b0f24ee62560ff85f12482d53fb83e1c4b964
Tx public key: f75d0a957e5b86997de401734d3c45470400c9bf83a136b588f48fd67d40d0d4
Timestamp: 1781019709 Timestamp [UTC]: 2026-06-09 15:41:49 Age [y:d:h:m:s]: 00:163:01:04:25
Block: 1555160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 126862 RingCT/type: yes/0
Extra: 01f75d0a957e5b86997de401734d3c45470400c9bf83a136b588f48fd67d40d0d4

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a829f89c0fc2ab6d101012cabe4153899c52632c7e3171cc702269cd128144ac 0.000600000000 2045138 of 15 <69>

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": 1555170, "vin": [ { "gen": { "height": 1555160 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a829f89c0fc2ab6d101012cabe4153899c52632c7e3171cc702269cd128144ac", "view_tag": "69" } } } ], "extra": [ 1, 247, 93, 10, 149, 126, 91, 134, 153, 125, 228, 1, 115, 77, 60, 69, 71, 4, 0, 201, 191, 131, 161, 54, 181, 136, 244, 143, 214, 125, 64, 208, 212 ], "rct_signatures": { "type": 0 } }


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