Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21deaf44f963da9dac0d9453391db476a40329b58d0c8bf9c8b483b599bff60a

Tx prefix hash: 742ff16d052d4cd6c278e9038e475f059293b998352d17432689ca344788ff7d
Tx public key: 2a40849ad41189600f0bd923e1e943688c5a16e31aefdcbc5fe48cdb7dd74af6
Timestamp: 1737719481 Timestamp [UTC]: 2025-01-24 11:51:21 Age [y:d:h:m:s]: 01:297:14:42:14
Block: 1204268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476549 RingCT/type: yes/0
Extra: 012a40849ad41189600f0bd923e1e943688c5a16e31aefdcbc5fe48cdb7dd74af60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c97244f7c65892993f5f3822ba6c39167e26aa135c137cb2e2e251333021973a 0.000600000000 1690953 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": 1204278, "vin": [ { "gen": { "height": 1204268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c97244f7c65892993f5f3822ba6c39167e26aa135c137cb2e2e251333021973a" } } ], "extra": [ 1, 42, 64, 132, 154, 212, 17, 137, 96, 15, 11, 217, 35, 225, 233, 67, 104, 140, 90, 22, 227, 26, 239, 220, 188, 95, 228, 140, 219, 125, 215, 74, 246, 2, 17, 0, 0, 0, 6, 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: