← previous blocknext block →recent activity
Analyzing
Block #100,878,099
12 transactions · 12 stateful · 2026-08-31 22:43:02 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,878,099 · 12 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
4w05w16w27w38w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c49736b…3418
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x33b5035a…d1c6
0x34b655…2a6f
4 touches
1 conflict
0x3d370aa5…d1cd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ebc22e7…0702
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x59bfb0ed…ebd2
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 0x7c49736b94…4d3418
Audit this contract →
← previous block·next block →recent activity