← previous blocknext block →recent activity
Analyzing
Block #101,803,037
13 transactions · 11 stateful · 2026-09-04 04:16:36 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,803,037 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0xfce0d821…352c
0x34b655…2a6f
4 touches
1 conflict
0x6a925e11…2653
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdbb571e4…6829
0x34b655…2a6f
4 touches
1 conflict
0x7f5b2c1d…0e7f
0x34b655…2a6f
2 touches
0 conflicts
0x9fbc6a76…9c29
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x0db691abac…993ee3
Audit this contract →
← previous block·next block →recent activity