Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0948dab5e128a651525077db7b157e80a9917b1db4f65b049ca9e625fec28ae7

Tx prefix hash: c7c861d48185400c34629d599ac74db4f411d98f710607e14e17329667fc3d9e
Tx public key: cfb567185c8668c0d1baa681d86b390da1d69349d82c96ea840ba1289edcedde
Timestamp: 1771571302 Timestamp [UTC]: 2026-02-20 07:08:22 Age [y:d:h:m:s]: 00:270:09:42:01
Block: 1481760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198746 RingCT/type: yes/0
Extra: 01cfb567185c8668c0d1baa681d86b390da1d69349d82c96ea840ba1289edcedde021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b0b2d53c7bffeda7e8ad4899bfd5bbf4c35c18c84473f331ac14a37d8c4964ff 0.000600000000 1971144 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": 1481770, "vin": [ { "gen": { "height": 1481760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0b2d53c7bffeda7e8ad4899bfd5bbf4c35c18c84473f331ac14a37d8c4964ff" } } ], "extra": [ 1, 207, 181, 103, 24, 92, 134, 104, 192, 209, 186, 166, 129, 216, 107, 57, 13, 161, 214, 147, 73, 216, 44, 150, 234, 132, 11, 161, 40, 158, 220, 237, 222, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: