Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 059e69dc7750a1c2df8f76d5d387fe2c7f9d86371c6b69e7ea8f7c16607d966d

Tx prefix hash: 04b2f39f62cfb5345129d8e6889df8d4dd2a7960ba7d4046cb27f1339fbe62d9
Tx public key: 03a6f186684c140f5abbd3efb3c2d071cfd6f6b9a027b579644ba0c462c514fd
Timestamp: 1779260192 Timestamp [UTC]: 2026-05-20 06:56:32 Age [y:d:h:m:s]: 00:181:17:56:45
Block: 1538809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 141956 RingCT/type: yes/0
Extra: 0103a6f186684c140f5abbd3efb3c2d071cfd6f6b9a027b579644ba0c462c514fd

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6180dd34ae3c0a9f8a272a25bdbe7741fd9779b23e6e605dcf9f30e3f019f339 0.000600000000 2028755 of 15 <7e>

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": 1538819, "vin": [ { "gen": { "height": 1538809 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "6180dd34ae3c0a9f8a272a25bdbe7741fd9779b23e6e605dcf9f30e3f019f339", "view_tag": "7e" } } } ], "extra": [ 1, 3, 166, 241, 134, 104, 76, 20, 15, 90, 187, 211, 239, 179, 194, 208, 113, 207, 214, 246, 185, 160, 39, 181, 121, 100, 75, 160, 196, 98, 197, 20, 253 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: