← previous blocknext block →recent activity
Analyzing
Block #100,926,140
10 transactions · 7 stateful · 2026-09-01 02:44:40 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,926,140 · 10 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7954a60…d294
0x34b655…2a6f
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0x894e3d9d…46c1
0x34b655…2a6f
4 touches
1 conflict
0x05286dbb…4517
0x34b655…2a6f
2 touches
0 conflicts
0x15127a2c…a744
0x34b655…2a6f
2 touches
0 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
2 touches
0 conflicts
0x20afc93b…24c6
0x34b655…2a6f
2 touches
0 conflicts
0x2ad2f4bc…1800
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 0xc7954a6095…b3d294
Audit this contract →
← previous block·next block →recent activity