← previous blocknext block →recent activity
Analyzing
Block #101,675,294
17 transactions · 14 stateful · 2026-09-03 17:34:06 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,675,294 · 17 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
2w03w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb58ed141…c32e
0x34b655…2a6f
4 touches
1 conflict
0xdac8e13c…bc65
0x34b655…2a6f
4 touches
1 conflict
0xe37b53a4…cd0f
0x34b655…2a6f
4 touches
1 conflict
0xf0800962…405f
0x34b655…2a6f
4 touches
1 conflict
0x0ffac39e…6d34
0x34b655…2a6f
4 touches
1 conflict
0x04972c2c…b990
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x477cb4f5…11b4
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
1 conflict on slot 0xb58ed141dc…9bc32e
Audit this contract →
← previous block·next block →recent activity