← previous blocknext block →recent activity
Analyzing
Block #100,732,357
14 transactions · 13 stateful · 2026-08-31 10:29:29 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,732,357 · 14 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
6w07w19w211w012w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x638c0ff8…58d1
0x34b655…2a6f
6 touches
3 conflicts
0x7462b8f2…6312
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x05cdc9b4…d6d3
0x34b655…2a6f
4 touches
1 conflict
0x14342429…3353
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x81716ce9…095f
0x34b655…2a6f
4 touches
1 conflict
0xc87e767e…4bba
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
3 conflicts on slot 0x638c0ff8f1…1d58d1
Audit this contract →
← previous block·next block →recent activity