← previous blocknext block →recent activity
Analyzing
Block #93,665,383
21 transactions · 19 stateful · 2026-08-06 15:08:58 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,665,383 · 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
2w03w04w15w06w111w117w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
4 touches
1 conflict
0x103be197…826c
0xa6afd3…d132
4 touches
1 conflict
0x605dab4d…167f
0x34b655…2a6f
4 touches
1 conflict
0x76faab64…5da0
0x34b655…2a6f
4 touches
1 conflict
0x8152ad3e…5486
0x34b655…2a6f
4 touches
1 conflict
0x990e8d73…7c45
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity