← previous blocknext block →recent activity
Analyzing
Block #100,118,684
24 transactions · 20 stateful · 2026-08-29 06:57:53 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.42
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,118,684 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w17w010w211w312w415w516w618w719w220w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8a8db2…8a6d
0x34b655…2a6f
12 touches
15 conflicts
0x1398e9f0…69ac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x04dbb52e…fe23
0x34b655…2a6f
10 touches
10 conflicts
0x758a0dd5…0f46
0x34b655…2a6f
8 touches
6 conflicts
0x35134740…1bb5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
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
15 conflicts on slot 0x5c8a8db2ad…f58a6d
Audit this contract →
← previous block·next block →recent activity