Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86d0a6b69d1f656d359deccda384121b5f134731d900b2bfad7a5d5a3e8c3403

Tx prefix hash: ad182af28c34b800ccf2bbcba058bf2e0870b9c2d137b9aaf78c761eb1a6050a
Tx public key: cc55e580e209665b5dcb36a9e10e089702b2f5c84476c0f1c88d413bedccfc71
Timestamp: 1794831535 Timestamp [UTC]: 2026-11-16 12:18:55 Age [y:d:h:m:s]: 00:003:10:00:22
Block: 1679643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 2561 RingCT/type: yes/0
Extra: 01cc55e580e209665b5dcb36a9e10e089702b2f5c84476c0f1c88d413bedccfc71

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 707da1cf9806c3d41f3a7f14c10a0f27cdd035e0a0056abc8bd324a2c5bd9b9a 0.000600000000 2170431 of 15 <60>

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": 1679653, "vin": [ { "gen": { "height": 1679643 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "707da1cf9806c3d41f3a7f14c10a0f27cdd035e0a0056abc8bd324a2c5bd9b9a", "view_tag": "60" } } } ], "extra": [ 1, 204, 85, 229, 128, 226, 9, 102, 91, 93, 203, 54, 169, 225, 14, 8, 151, 2, 178, 245, 200, 68, 118, 192, 241, 200, 141, 65, 59, 237, 204, 252, 113 ], "rct_signatures": { "type": 0 } }


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