← previous blocknext block →recent activity
Analyzing
Block #102,571,233
13 transactions · 13 stateful · 2026-09-06 21:07:02 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,571,233 · 13 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
6w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1d8e5c2…61f2
0x34b655…2a6f
4 touches
1 conflict
0x2f02d4df…3567
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x1f459632…a5d9
0x34b655…2a6f
4 touches
1 conflict
0x5e47cbde…9659
0x34b655…2a6f
2 touches
0 conflicts
0x6a0a8b19…c3b0
0x34b655…2a6f
2 touches
0 conflicts
0x7354c4f2…c3b6
0x34b655…2a6f
2 touches
0 conflicts
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 0xe1d8e5c26f…3c61f2
Audit this contract →
← previous block·next block →recent activity