← previous blocknext block →recent activity
Analyzing
Block #93,357,286
19 transactions · 19 stateful · 2026-08-05 13:20:05 UTC
Parallelism
84/100
Blocked
37%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,357,286 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w07w110w215w116w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x35c429dc…0201
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0x6b564d99…b9eb
0x34b655…2a6f
4 touches
1 conflict
0x6b564d99…b9ec
0x34b655…2a6f
4 touches
1 conflict
0x700c7319…e584
0x34b655…2a6f
4 touches
1 conflict
0x71efc59e…1434
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
1 conflict on slot 0x30ae635d6d…0f5e67
Audit this contract →
← previous block·next block →recent activity