Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 606c68b1a4da4ba415130f38de6d0f4874cefa27b0f838cc0c58c2beabbc376d

Tx prefix hash: 47f8015c7ab7b9982bc2052c68de6ed10b8d81fd498c55562c8e1f37ebe89772
Tx public key: ed34bed58d5583ac6eea02ee2af2348639cb4192c3dd22ca358694d8c4dddec6
Timestamp: 1756571269 Timestamp [UTC]: 2025-08-30 16:27:49 Age [y:d:h:m:s]: 00:257:17:44:25
Block: 1357785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176515 RingCT/type: yes/0
Extra: 01ed34bed58d5583ac6eea02ee2af2348639cb4192c3dd22ca358694d8c4dddec6021100000004ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a387635d2cb475bea56e14c6820c7e5adefa0b01f802168f4f961ab899a2ae6a 0.000600000000 1845794 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": 1357795, "vin": [ { "gen": { "height": 1357785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a387635d2cb475bea56e14c6820c7e5adefa0b01f802168f4f961ab899a2ae6a" } } ], "extra": [ 1, 237, 52, 190, 213, 141, 85, 131, 172, 110, 234, 2, 238, 42, 242, 52, 134, 57, 203, 65, 146, 195, 221, 34, 202, 53, 134, 148, 216, 196, 221, 222, 198, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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: