← previous blocknext block →recent activity
Analyzing
Block #93,550,215
21 transactions · 17 stateful · 2026-08-06 05:30:00 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,550,215 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w110w211w012w113w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x84f70c64…8d48
0x065c9d…c394
4 touches
1 conflict
0x446f2734…8b54
0x0a3323…0a3c
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x52c63247…ce02
0x0a3323…0a3c
4 touches
1 conflict
0xd676e291…3ecf
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: MarginAccount
3 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity