← previous blocknext block →recent activity
Analyzing
Block #100,751,055
30 transactions · 23 stateful · 2026-08-31 12:03:32 UTC
Parallelism
90/100
Blocked
39%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,751,055 · 30 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
1w02w16w07w19w013w015w118w019w120w221w125w127w229w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99361d12…a19a
0x34b655…2a6f
6 touches
3 conflicts
0x62d019cf…40b8
0xd32edf…ff58
5 touches
3 conflicts
0x3f2100d8…f9b5
0xa6afd3…d132
4 touches
1 conflict
0x7ea1cfdf…81c0
0xa6afd3…d132
4 touches
1 conflict
0xb26ff3de…9352
0xa6afd3…d132
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
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 0x99361d1219…10a19a
Audit this contract →
← previous block·next block →recent activity