Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bfa9da0bb5872d3765c8e8ffddc0526f7926c6aaddb221aee373b88ea9a518c

Tx prefix hash: b3fa87b7dedaa49c94c362c49d5a45925244e5050f39b4ae1c031829dbf38f3b
Tx public key: 0864c46f7b28e93b1ca0b163ea18e3e3bce416e27d27573b145217ed2bdc0a47
Timestamp: 1791565133 Timestamp [UTC]: 2026-10-09 16:58:53 Age [y:d:h:m:s]: 00:037:18:49:05
Block: 1650790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 28841 RingCT/type: yes/0
Extra: 010864c46f7b28e93b1ca0b163ea18e3e3bce416e27d27573b145217ed2bdc0a47

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e7ab1ab642c5808f2789c9374a5ea706a884fde5f43885c1d73f2f074fe57cbd 0.000600000000 2140946 of 15 <81>

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": 1650800, "vin": [ { "gen": { "height": 1650790 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "e7ab1ab642c5808f2789c9374a5ea706a884fde5f43885c1d73f2f074fe57cbd", "view_tag": "81" } } } ], "extra": [ 1, 8, 100, 196, 111, 123, 40, 233, 59, 28, 160, 177, 99, 234, 24, 227, 227, 188, 228, 22, 226, 125, 39, 87, 59, 20, 82, 23, 237, 43, 220, 10, 71 ], "rct_signatures": { "type": 0 } }


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