← previous blocknext block →recent activity
Analyzing
Block #100,628,217
20 transactions · 17 stateful · 2026-08-31 01:45:38 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,628,217 · 20 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
3w05w06w010w111w212w213w215w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00500a94…20d5
0x34b655…2a6f
6 touches
3 conflicts
0xead15497…1dbe
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5684aadd…8d62
0x34b655…2a6f
4 touches
1 conflict
0x7a7030a4…bc0d
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 0x00500a94bf…5a20d5
Audit this contract →
← previous block·next block →recent activity