← previous blocknext block →recent activity
Analyzing
Block #103,214,848
18 transactions · 18 stateful · 2026-09-09 03:12:55 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.89
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,214,848 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w110w211w312w313w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x7504da64…542f
0x34b655…2a6f
6 touches
3 conflicts
0x5202469c…bec0
0x34b655…2a6f
6 touches
3 conflicts
0x7c68d10b…8386
0x34b655…2a6f
6 touches
3 conflicts
0x0f13b598…f75b
0x34b655…2a6f
6 touches
3 conflicts
0xc572e121…f1be
0x34b655…2a6f
6 touches
3 conflicts
0x059a20f2…b7a5
0x34b655…2a6f
4 touches
1 conflict
0x7c774f33…6ecf
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
6 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity