← previous blocknext block →recent activity
Analyzing
Block #100,139,434
9 transactions · 9 stateful · 2026-08-29 08:42:29 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,139,434 · 9 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
4w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x191e0467…70e5
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x605e358e…dc99
0x34b655…2a6f
4 touches
1 conflict
0x8f267c0d…ebba
0x34b655…2a6f
4 touches
1 conflict
0x03fe6234…08de
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…004b
0x80c745…7210
2 touches
0 conflicts
0x00000000…004c
0x80c745…7210
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity