← previous blocknext block →recent activity
Analyzing
Block #100,559,783
16 transactions · 16 stateful · 2026-08-30 20:01:23 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,559,783 · 16 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
3w04w16w07w19w010w111w212w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6324ccc9…14fd
0x34b655…2a6f
6 touches
3 conflicts
0xea57afd0…4232
0x34b655…2a6f
6 touches
3 conflicts
0x10d80fee…dbda
0x2b46c0…1669
4 touches
1 conflict
0x595839b9…ca61
0x2b46c0…1669
4 touches
1 conflict
0x7aa91b8f…d070
0x2b46c0…1669
4 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6a9d
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6a9e
0x2b46c0…1669
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 0x6324ccc962…7f14fd
Audit this contract →
← previous block·next block →recent activity