Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d12d1a49d40cd6e28897fdb1f478d8f84946f392aceb845094de7e1035a726dd

Tx prefix hash: cddca9f8563c29db7b0908545c5c20ebe0f6e75dab3cde2e6ed23352b92b92ed
Tx public key: dd5bfc144ea2907e3d2ffc51afb5f8cc9c0cdae5fd0e9a690c6c6066614271b7
Timestamp: 1752698451 Timestamp [UTC]: 2025-07-16 20:40:51 Age [y:d:h:m:s]: 01:120:19:12:14
Block: 1326939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351303 RingCT/type: yes/0
Extra: 01dd5bfc144ea2907e3d2ffc51afb5f8cc9c0cdae5fd0e9a690c6c6066614271b702110000000301491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 08799b2c2800dd4d02c1e091be621f56751166a28b151225a3f32de13ecad4f8 0.000600000000 1814692 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": 1326949, "vin": [ { "gen": { "height": 1326939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08799b2c2800dd4d02c1e091be621f56751166a28b151225a3f32de13ecad4f8" } } ], "extra": [ 1, 221, 91, 252, 20, 78, 162, 144, 126, 61, 47, 252, 81, 175, 181, 248, 204, 156, 12, 218, 229, 253, 14, 154, 105, 12, 108, 96, 102, 97, 66, 113, 183, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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: