← previous blocknext block →recent activity
Analyzing
Block #100,985,135
29 transactions · 21 stateful · 2026-09-01 07:41:26 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,985,135 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w110w011w112w213w316w017w118w219w321w422w526w328w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8311570f…5321
0x34b655…2a6f
10 touches
10 conflicts
0xa952c504…7b64
0x34b655…2a6f
8 touches
6 conflicts
0x714be73e…a11e
0x34b655…2a6f
6 touches
3 conflicts
0xb157841c…54c2
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xea2d3331…6e37
0x1b6862…e19c
4 touches
1 conflict
0x101726f8…bf51
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
10 conflicts on slot 0x8311570feb…ae5321
Audit this contract →
← previous block·next block →recent activity