← previous blocknext block →recent activity
Analyzing
Block #93,349,636
20 transactions · 19 stateful · 2026-08-05 12:41:37 UTC
Parallelism
65/100
Blocked
37%
Avg conflicts / tx
0.55
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,349,636 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w29w210w313w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87fcd5db…d2e6
0x34b655…2a6f
6 touches
3 conflicts
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xe7757e15…d09e
0x34b655…2a6f
4 touches
1 conflict
0x05b1b07a…7a99
0x34b655…2a6f
4 touches
1 conflict
0x805d08cf…3cfc
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: Perpl
3 conflicts on slot 0x87fcd5db2b…26d2e6
Audit this contract →
← previous block·next block →recent activity