← previous blocknext block →recent activity
Analyzing
Block #100,926,218
21 transactions · 18 stateful · 2026-09-01 02:45:04 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,926,218 · 21 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
1w013w014w115w016w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8cadee4…1bef
0x34b655…2a6f
6 touches
3 conflicts
0xa538600d…3da5
0x851145…3f07
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x25180879…8191
0x34b655…2a6f
4 touches
1 conflict
0x4147b177…c9ba
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x72507c50…15eb
0x34b655…2a6f
4 touches
1 conflict
0xb358a740…cf65
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 0xc8cadee478…5f1bef
Audit this contract →
← previous block·next block →recent activity