Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b575863802d51303e97c81f2d476c2c295ffc22c64adfbc0150bca2c4a477c13

Tx prefix hash: a3278f9da7f05d5718390907f727a79f92b635d0e05814dfce9229b20eac5836
Tx public key: 442a83505d9ec6a0e61ae64c3b85d175b38fe0ac9e3cde3360a88e1b6cb81d34
Timestamp: 1736999512 Timestamp [UTC]: 2025-01-16 03:51:52 Age [y:d:h:m:s]: 01:305:09:06:59
Block: 1198338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482052 RingCT/type: yes/0
Extra: 01442a83505d9ec6a0e61ae64c3b85d175b38fe0ac9e3cde3360a88e1b6cb81d3402110000000201491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 204a87712c5b8a9481047cfd369d6091674139fc56a61b5e31f1ed1efc50f31f 0.000600000000 1684961 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": 1198348, "vin": [ { "gen": { "height": 1198338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "204a87712c5b8a9481047cfd369d6091674139fc56a61b5e31f1ed1efc50f31f" } } ], "extra": [ 1, 68, 42, 131, 80, 93, 158, 198, 160, 230, 26, 230, 76, 59, 133, 209, 117, 179, 143, 224, 172, 158, 60, 222, 51, 96, 168, 142, 27, 108, 184, 29, 52, 2, 17, 0, 0, 0, 2, 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: