← previous blocknext block →recent activity
Analyzing
Block #100,733,381
11 transactions · 11 stateful · 2026-08-31 10:34:38 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,733,381 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac389ba9…8b45
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe9c09c87…d898
0x34b655…2a6f
4 touches
1 conflict
0x382434ca…96b5
0x34b655…2a6f
2 touches
0 conflicts
0x54bf3074…cb35
0x34b655…2a6f
2 touches
0 conflicts
0x9210e826…1414
0x34b655…2a6f
2 touches
0 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
2 touches
0 conflicts
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 0xac389ba9d1…e18b45
Audit this contract →
← previous block·next block →recent activity