← previous blocknext block →recent activity
Analyzing
Block #102,518,195
50 transactions · 50 stateful · 2026-09-06 16:38:03 UTC
Parallelism
96/100
Blocked
6%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,518,195 · 50 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
1w08w045w147w148w049w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9874e36…beed
0x34b655…2a6f
4 touches
1 conflict
0x16d77246…bac5
0x34b655…2a6f
4 touches
1 conflict
0x1a7c7664…c996
0x34b655…2a6f
4 touches
1 conflict
0x21e79ad8…c5db
0x34b655…2a6f
4 touches
1 conflict
0x290abc80…f605
0x34b655…2a6f
4 touches
1 conflict
0x324e135c…89ef
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xf9874e3690…90beed
Audit this contract →
← previous block·next block →recent activity