Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 774f4c38f1f2d525bae86bb87bbf2c1b0377312002ce998e41f1f15123e6b2fe

Tx prefix hash: 8702dde6b3dbc79bc44d1305ceb4ba611dc671b79465116c08078864848647cb
Tx public key: 14e44c896bb2fa40c9f9101178fa1f2141624c1aa283e9cb214e243458725b4a
Timestamp: 1749349578 Timestamp [UTC]: 2025-06-08 02:26:18 Age [y:d:h:m:s]: 00:337:17:41:48
Block: 1300324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231214 RingCT/type: yes/0
Extra: 0114e44c896bb2fa40c9f9101178fa1f2141624c1aa283e9cb214e243458725b4a021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d758d77a9beb4c47dcf620482815491f5a5d8c20e1fdbed0ce5d1d84873a4f62 0.000600000000 1787873 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": 1300334, "vin": [ { "gen": { "height": 1300324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d758d77a9beb4c47dcf620482815491f5a5d8c20e1fdbed0ce5d1d84873a4f62" } } ], "extra": [ 1, 20, 228, 76, 137, 107, 178, 250, 64, 201, 249, 16, 17, 120, 250, 31, 33, 65, 98, 76, 26, 162, 131, 233, 203, 33, 78, 36, 52, 88, 114, 91, 74, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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: