Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cde8486f75de88f1e39d395262fd385684ea114eef8dbcd297e6587ecf7f7eb1

Tx prefix hash: 88e81e12ee5985fb6eaf14af6806d3d7c23e0a3a37f5e01ad343ca65dc2a3f01
Tx public key: 6ddfaee86e79fb2c5f4bea0a2716a81193f64f0116087d86fb42f29026a31572
Timestamp: 1742077742 Timestamp [UTC]: 2025-03-15 22:29:02 Age [y:d:h:m:s]: 01:250:13:02:39
Block: 1240149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443232 RingCT/type: yes/0
Extra: 016ddfaee86e79fb2c5f4bea0a2716a81193f64f0116087d86fb42f29026a31572021100000018007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6d1498e5b116c21f5f3aaf9bf98efc18c5ce7e59e1f08d33fb1589085c9a51eb 0.000600000000 1727114 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": 1240159, "vin": [ { "gen": { "height": 1240149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d1498e5b116c21f5f3aaf9bf98efc18c5ce7e59e1f08d33fb1589085c9a51eb" } } ], "extra": [ 1, 109, 223, 174, 232, 110, 121, 251, 44, 95, 75, 234, 10, 39, 22, 168, 17, 147, 246, 79, 1, 22, 8, 125, 134, 251, 66, 242, 144, 38, 163, 21, 114, 2, 17, 0, 0, 0, 24, 0, 127, 151, 138, 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: