← previous blocknext block →recent activity
Analyzing
Block #100,140,968
19 transactions · 17 stateful · 2026-08-29 08:50:12 UTC
Parallelism
84/100
Blocked
18%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,140,968 · 19 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
1w02w13w24w011w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa11b60f7…8e8b
0x34b655…2a6f
4 touches
1 conflict
0xdcbe6c3e…f8ed
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x50c61506…343f
0x34b655…2a6f
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0x45f562b2…9294
0x2b46c0…1669
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 0xa11b60f7c7…f88e8b
Audit this contract →
← previous block·next block →recent activity