← previous blocknext block →recent activity
Analyzing
Block #102,446,360
21 transactions · 21 stateful · 2026-09-06 10:33:43 UTC
Parallelism
90/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,446,360 · 21 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
5w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23b1a214…ccb9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x01e6de23…d3d5
0x34b655…2a6f
2 touches
0 conflicts
0x192ad33c…ef97
0x34b655…2a6f
2 touches
0 conflicts
0x24073d82…df9f
0x34b655…2a6f
2 touches
0 conflicts
0x312e4698…54c0
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 0x23b1a214dd…4cccb9
Audit this contract →
← previous block·next block →recent activity