Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c30a4286a4da31832130f39d329dfcd3b9577affaa44f3bb9e53324ebd8af4ca

Tx prefix hash: 161fbe0c81f92b42688d0b4513ade54cadc635b09c88e7ceb8c497a2863bf7a9
Tx public key: 090725e2f69dcc9dadcaf2a8278970494face0273a6e16368b32d6bc92e4106d
Timestamp: 1740142203 Timestamp [UTC]: 2025-02-21 12:50:03 Age [y:d:h:m:s]: 01:269:05:25:50
Block: 1224065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456490 RingCT/type: yes/0
Extra: 01090725e2f69dcc9dadcaf2a8278970494face0273a6e16368b32d6bc92e4106d0211000000141f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: df8d2bfb808699f3b56b4e9417e07170e1cdc616d61b3ab67508d55eca0a3cef 0.000600000000 1710922 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": 1224075, "vin": [ { "gen": { "height": 1224065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df8d2bfb808699f3b56b4e9417e07170e1cdc616d61b3ab67508d55eca0a3cef" } } ], "extra": [ 1, 9, 7, 37, 226, 246, 157, 204, 157, 173, 202, 242, 168, 39, 137, 112, 73, 79, 172, 224, 39, 58, 110, 22, 54, 139, 50, 214, 188, 146, 228, 16, 109, 2, 17, 0, 0, 0, 20, 31, 10, 83, 235, 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: