Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1763c21cddcfac424a7b1ca2d90f0192feb2473bd1b62b67a1ae4253eae83c4

Tx prefix hash: 521df53b5abae1241ba9a493687aae3bb44d306de917fa22e68d36314f625d53
Tx public key: 2527eea2272e05e99ca20cba6959d5a1fac8f88a8d79ffcb84a6f34be5fe4a51
Timestamp: 1750285927 Timestamp [UTC]: 2025-06-18 22:32:07 Age [y:d:h:m:s]: 01:153:20:44:32
Block: 1307942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374159 RingCT/type: yes/0
Extra: 012527eea2272e05e99ca20cba6959d5a1fac8f88a8d79ffcb84a6f34be5fe4a5102110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 33692980ccb94c01e51fd71f7137673b75a3c60f79caa0ab0667aa78ea39aedd 0.000600000000 1795553 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": 1307952, "vin": [ { "gen": { "height": 1307942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33692980ccb94c01e51fd71f7137673b75a3c60f79caa0ab0667aa78ea39aedd" } } ], "extra": [ 1, 37, 39, 238, 162, 39, 46, 5, 233, 156, 162, 12, 186, 105, 89, 213, 161, 250, 200, 248, 138, 141, 121, 255, 203, 132, 166, 243, 75, 229, 254, 74, 81, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: