Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24b9b55d009e2e07fc42d6da30c085f9530d1027c6d7e3bafa65dea3416c9f32

Tx prefix hash: 908ef5af8b7632e6fc9b23bdb67553e17d61c4ce5f5cc5eb407570996a240b11
Tx public key: 527c2ac781a241654a0ffb2380e8bc914554b04dddae4b49e871a0b57ed808ed
Timestamp: 1750066583 Timestamp [UTC]: 2025-06-16 09:36:23 Age [y:d:h:m:s]: 01:157:16:23:55
Block: 1306145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376949 RingCT/type: yes/0
Extra: 01527c2ac781a241654a0ffb2380e8bc914554b04dddae4b49e871a0b57ed808ed02110000000443846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 046a6a387bc3ab39541e6ec16044b4da545a7c9a9c9fc6c7c2c0156b9d31ac12 0.000600000000 1793748 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": 1306155, "vin": [ { "gen": { "height": 1306145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "046a6a387bc3ab39541e6ec16044b4da545a7c9a9c9fc6c7c2c0156b9d31ac12" } } ], "extra": [ 1, 82, 124, 42, 199, 129, 162, 65, 101, 74, 15, 251, 35, 128, 232, 188, 145, 69, 84, 176, 77, 221, 174, 75, 73, 232, 113, 160, 181, 126, 216, 8, 237, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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: