← previous blocknext block →recent activity
Analyzing
Block #100,747,949
22 transactions · 21 stateful · 2026-08-31 11:47:55 UTC
Parallelism
77/100
Blocked
19%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,747,949 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w39w010w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc2493d3…6898
0x34b655…2a6f
8 touches
6 conflicts
0x869ee5a8…3463
0x34b655…2a6f
8 touches
6 conflicts
0xb28cb6ae…2398
0x34b655…2a6f
6 touches
3 conflicts
0xc87e767e…4bba
0x34b655…2a6f
4 touches
1 conflict
0xfb856b8c…7557
0x34b655…2a6f
4 touches
1 conflict
0x5fde4971…aac9
0x34b655…2a6f
4 touches
1 conflict
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0xa0c75a07…1ac1
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
6 conflicts on slot 0xfc2493d371…f36898
Audit this contract →
← previous block·next block →recent activity