← previous blocknext block →recent activity
Analyzing
Block #101,662,398
14 transactions · 14 stateful · 2026-09-03 16:29:13 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,662,398 · 14 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
3w04w05w16w09w110w212w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f0f48f1…646d
0x34b655…2a6f
6 touches
3 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
4 touches
1 conflict
0x970667dd…fb66
0x34b655…2a6f
4 touches
1 conflict
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0xbd22d0fc…64fd
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x8f0f48f15c…b6646d
Audit this contract →
← previous block·next block →recent activity