← previous blocknext block →recent activity
Analyzing
Block #101,681,924
12 transactions · 10 stateful · 2026-09-03 18:07:27 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,681,924 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9935284…f313
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
6 touches
3 conflicts
0xd41f5136…97c6
0x34b655…2a6f
6 touches
3 conflicts
0x48203298…65cb
0x34b655…2a6f
4 touches
1 conflict
0x21a4d924…f40c
0x34b655…2a6f
4 touches
1 conflict
0x4736f680…60d2
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 0xf99352848d…74f313
Audit this contract →
← previous block·next block →recent activity