← previous blocknext block →recent activity
Analyzing
Block #100,728,997
27 transactions · 18 stateful · 2026-08-31 10:12:35 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,728,997 · 27 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
1w02w14w06w07w19w014w117w218w319w221w426w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13bc9f0a…cce9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x79347b24…9fba
0x34b655…2a6f
6 touches
3 conflicts
0x4a45b318…9716
0x34b655…2a6f
4 touches
1 conflict
0x54c6fb44…369a
0x34b655…2a6f
4 touches
1 conflict
0x68531239…e9a3
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x8dd44b51…56f3
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 0x13bc9f0ab3…0dcce9
Audit this contract →
← previous block·next block →recent activity