Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b65ee4f743f0b1e8d88f3f780bcaa6f82fa66582c9fd08b6c890ccfc2dc43ef7

Tx prefix hash: 9628b4b157e22660ec106e792b20534a2872f4f16185c02da1264a7faf334cbb
Tx public key: 656703ce819ccea805d8097e139ed0a1b412dc8505b994e5746da86327d49c4b
Timestamp: 1774773140 Timestamp [UTC]: 2026-03-29 08:32:20 Age [y:d:h:m:s]: 00:233:07:18:52
Block: 1508247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172226 RingCT/type: yes/0
Extra: 01656703ce819ccea805d8097e139ed0a1b412dc8505b994e5746da86327d49c4b021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c46468dd2dc17285a877e9913cbf4245821a47a655b8531b036da1cbf1b54996 0.000600000000 1997999 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": 1508257, "vin": [ { "gen": { "height": 1508247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c46468dd2dc17285a877e9913cbf4245821a47a655b8531b036da1cbf1b54996" } } ], "extra": [ 1, 101, 103, 3, 206, 129, 156, 206, 168, 5, 216, 9, 126, 19, 158, 208, 161, 180, 18, 220, 133, 5, 185, 148, 229, 116, 109, 168, 99, 39, 212, 156, 75, 2, 17, 0, 0, 0, 7, 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: