← previous blocknext block →recent activity
Analyzing
Block #101,798,655
20 transactions · 16 stateful · 2026-09-04 03:54:34 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,798,655 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51d0a65c…5e21
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xe8f860c0…35c9
0x34b655…2a6f
6 touches
3 conflicts
0x3d13406e…eff1
0x34b655…2a6f
6 touches
3 conflicts
0x4dffc33e…068d
0x34b655…2a6f
6 touches
3 conflicts
0x4f3cc09a…2804
0x34b655…2a6f
6 touches
3 conflicts
0xab52434a…df3b
0x34b655…2a6f
6 touches
3 conflicts
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 0x51d0a65c90…045e21
Audit this contract →
← previous block·next block →recent activity