Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1f5bddcf4c1f58ec315e6dd5f62fd1992c1cc3e41e43292363af816c8cce6e

Tx prefix hash: 24455b486b5cd95e87d22f48e5e5dbd9cbd59718211044d8f466e2c6ae55e737
Tx public key: 578988985275cd6ff6b91ff9b3563928af24f8206f5c8afa27d6e547e4935041
Timestamp: 1753538601 Timestamp [UTC]: 2025-07-26 14:03:21 Age [y:d:h:m:s]: 00:290:13:41:08
Block: 1333835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198732 RingCT/type: yes/0
Extra: 01578988985275cd6ff6b91ff9b3563928af24f8206f5c8afa27d6e547e4935041021100000005db6acbd3000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1603fc0d344db27fb8ae3e7fae8f84bd3e8de59f5c8637862affa70e3979ce6e 0.000600000000 1821634 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": 1333845, "vin": [ { "gen": { "height": 1333835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1603fc0d344db27fb8ae3e7fae8f84bd3e8de59f5c8637862affa70e3979ce6e" } } ], "extra": [ 1, 87, 137, 136, 152, 82, 117, 205, 111, 246, 185, 31, 249, 179, 86, 57, 40, 175, 36, 248, 32, 111, 92, 138, 250, 39, 214, 229, 71, 228, 147, 80, 65, 2, 17, 0, 0, 0, 5, 219, 106, 203, 211, 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: