← previous blocknext block →recent activity
Analyzing
Block #100,984,074
20 transactions · 20 stateful · 2026-09-01 07:36:05 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,984,074 · 20 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
3w04w15w07w18w09w111w012w113w014w115w217w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe188ad90…d23f
0x34b655…2a6f
6 touches
3 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x1fb6e47f…b99a
0x34b655…2a6f
4 touches
1 conflict
0x4bb4d9a2…62bc
0x34b655…2a6f
4 touches
1 conflict
0x8cfa9962…2675
0x34b655…2a6f
4 touches
1 conflict
0xb7e8b0c4…dec3
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 0xe188ad90a8…5bd23f
Audit this contract →
← previous block·next block →recent activity