Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3f061876cbf48e12dfb3e9a0a40ea394abc4534f857a8e2acf41921e29e330e

Tx prefix hash: c01f22437e9ac07abbb1f746e26d3ecd860e08550b12bf0bd5760dee1c2c44e6
Tx public key: fb7509893206b8741be0a3162ee8c354aa0ad8efa2ddac599051be43b5a3d86d
Timestamp: 1772497629 Timestamp [UTC]: 2026-03-03 00:27:09 Age [y:d:h:m:s]: 00:257:22:29:26
Block: 1489420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189799 RingCT/type: yes/0
Extra: 01fb7509893206b8741be0a3162ee8c354aa0ad8efa2ddac599051be43b5a3d86d021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b1649d683178ff413c4e769c059650d3a0af0b8e512f5b293a6c2f52b9142780 0.000600000000 1978910 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": 1489430, "vin": [ { "gen": { "height": 1489420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1649d683178ff413c4e769c059650d3a0af0b8e512f5b293a6c2f52b9142780" } } ], "extra": [ 1, 251, 117, 9, 137, 50, 6, 184, 116, 27, 224, 163, 22, 46, 232, 195, 84, 170, 10, 216, 239, 162, 221, 172, 89, 144, 81, 190, 67, 181, 163, 216, 109, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: