Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0efdb38f062cb3161ebe8dc8d3ab25f9ee77a4514e83b2368bed2e43476ce79b

Tx prefix hash: e07986ff9b71d528e84b4f4fe396b8aa0a38d428c506d318cd9729ce6844bd8f
Tx public key: b5b5d2bf95e88176718eef12f32715c5c367caefa840a58d0594912dfd0a49ec
Timestamp: 1740431949 Timestamp [UTC]: 2025-02-24 21:19:09 Age [y:d:h:m:s]: 01:263:09:43:14
Block: 1226477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452241 RingCT/type: yes/0
Extra: 01b5b5d2bf95e88176718eef12f32715c5c367caefa840a58d0594912dfd0a49ec0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf534db7f04a6a1c3c088e4e98dc7481d4a6410f15517788e2d97d04cc8b4d6c 0.000600000000 1713348 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": 1226487, "vin": [ { "gen": { "height": 1226477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf534db7f04a6a1c3c088e4e98dc7481d4a6410f15517788e2d97d04cc8b4d6c" } } ], "extra": [ 1, 181, 181, 210, 191, 149, 232, 129, 118, 113, 142, 239, 18, 243, 39, 21, 197, 195, 103, 202, 239, 168, 64, 165, 141, 5, 148, 145, 45, 253, 10, 73, 236, 2, 17, 0, 0, 0, 1, 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: