Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c70212b190fc937294b07dfc3a3ffe233a215fb393dc82e612770043e424d2e5

Tx prefix hash: 9315e8bbc074f41432d9f9026bb57d528790f22de71823f0d5e7fd3c8cd8255a
Tx public key: 1278f8056cc6246b457ceb2f68d539d669ac14e90df677f2b250eab8018f6b8f
Timestamp: 1773250128 Timestamp [UTC]: 2026-03-11 17:28:48 Age [y:d:h:m:s]: 00:252:22:04:42
Block: 1495646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186335 RingCT/type: yes/0
Extra: 011278f8056cc6246b457ceb2f68d539d669ac14e90df677f2b250eab8018f6b8f021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 599500acf70eb95445322089a3d5bc88a5a599c34db4703c397444ffa7ac2944 0.000600000000 1985258 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": 1495656, "vin": [ { "gen": { "height": 1495646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "599500acf70eb95445322089a3d5bc88a5a599c34db4703c397444ffa7ac2944" } } ], "extra": [ 1, 18, 120, 248, 5, 108, 198, 36, 107, 69, 124, 235, 47, 104, 213, 57, 214, 105, 172, 20, 233, 13, 246, 119, 242, 178, 80, 234, 184, 1, 143, 107, 143, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: