← previous blocknext block →recent activity
Analyzing
Block #102,444,295
13 transactions · 13 stateful · 2026-09-06 10:23:18 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,444,295 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w110w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf60062ab…f98d
0x34b655…2a6f
4 touches
1 conflict
0xe9c2eade…425e
0x34b655…2a6f
4 touches
1 conflict
0xed19fb96…2166
0x34b655…2a6f
4 touches
1 conflict
0xf60062ab…f98c
0x34b655…2a6f
4 touches
1 conflict
0x3500214b…e9da
0x34b655…2a6f
4 touches
1 conflict
0x53c41998…7d52
0x34b655…2a6f
4 touches
1 conflict
0x70d81211…f49f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xf60062ab4e…aef98d
Audit this contract →
← previous block·next block →recent activity