Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 224ed39312995335a8a9f9f0ab847a0f896e2be4472266176a748b2fe7559f70

Tx prefix hash: b085aa0bb2cc138474b792b6a2d8fd9a6e728d41075da8511b5a7b284346e21d
Tx public key: 16d9babd919efe46d61e508707438817f33350aceb53cac279944db367f46f9e
Timestamp: 1774926175 Timestamp [UTC]: 2026-03-31 03:02:55 Age [y:d:h:m:s]: 00:229:10:55:07
Block: 1509506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169436 RingCT/type: yes/0
Extra: 0116d9babd919efe46d61e508707438817f33350aceb53cac279944db367f46f9e021100000001ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7e956b1de7c0ab9206ae0cde2283f6fc92764af8db5bd53b351cafa8d06e3a54 0.000600000000 1999282 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": 1509516, "vin": [ { "gen": { "height": 1509506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e956b1de7c0ab9206ae0cde2283f6fc92764af8db5bd53b351cafa8d06e3a54" } } ], "extra": [ 1, 22, 217, 186, 189, 145, 158, 254, 70, 214, 30, 80, 135, 7, 67, 136, 23, 243, 51, 80, 172, 235, 83, 202, 194, 121, 148, 77, 179, 103, 244, 111, 158, 2, 17, 0, 0, 0, 1, 238, 75, 113, 129, 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: