← previous blocknext block →recent activity
Analyzing
Block #102,483,516
28 transactions · 27 stateful · 2026-09-06 13:42:06 UTC
Parallelism
89/100
Blocked
26%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,483,516 · 28 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
1w03w17w18w09w110w011w112w214w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88bfd4c1…3190
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
3 conflicts on slot 0x88bfd4c1f6…b63190
Audit this contract →
← previous block·next block →recent activity