Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8a38a3c248742cc90a4a05950ff3fbb32d0da9256f356454461b3e4bcc2074f

Tx prefix hash: b5503ff42dfe1d6a7a1df07c4972eb182752b81d6d47853edddcbbed5e353f5c
Tx public key: 7053a063d647c3cc8dc5fa8d250fa511f1e7b1de593ea9afb33c132d515f3f85
Timestamp: 1740576692 Timestamp [UTC]: 2025-02-26 13:31:32 Age [y:d:h:m:s]: 01:267:01:19:32
Block: 1227683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455081 RingCT/type: yes/0
Extra: 017053a063d647c3cc8dc5fa8d250fa511f1e7b1de593ea9afb33c132d515f3f850211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 32aecb25c8a931d0a0f8a8a0c5038b7d1283445ac56fb381daf09920dab37739 0.000600000000 1714558 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": 1227693, "vin": [ { "gen": { "height": 1227683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32aecb25c8a931d0a0f8a8a0c5038b7d1283445ac56fb381daf09920dab37739" } } ], "extra": [ 1, 112, 83, 160, 99, 214, 71, 195, 204, 141, 197, 250, 141, 37, 15, 165, 17, 241, 231, 177, 222, 89, 62, 169, 175, 179, 60, 19, 45, 81, 95, 63, 133, 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: