← previous blocknext block →recent activity
Analyzing
Block #101,668,027
13 transactions · 12 stateful · 2026-09-03 16:57:32 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,668,027 · 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
2w03w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeceefd39…ef67
0x34b655…2a6f
4 touches
1 conflict
0x9b6d3aab…11d2
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0145aa28…106b
0x34b655…2a6f
2 touches
0 conflicts
0x06e3db3a…1bc3
0x34b655…2a6f
2 touches
0 conflicts
0x0b7b942e…f3f4
0x34b655…2a6f
2 touches
0 conflicts
0x0f00fbe1…2815
0x34b655…2a6f
2 touches
0 conflicts
0x230b0b56…a675
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 0xeceefd39ec…deef67
Audit this contract →
← previous block·next block →recent activity