← previous blocknext block →recent activity
Analyzing
Block #102,063,181
19 transactions · 19 stateful · 2026-09-05 02:11:59 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,063,181 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w07w18w211w314w415w116w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62bb20db…431e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xeae7618e…b78e
0x34b655…2a6f
6 touches
3 conflicts
0x1dc71894…1884
0x34b655…2a6f
4 touches
1 conflict
0x2e1f5171…ad2d
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x5bb9a2e6…8376
0x34b655…2a6f
4 touches
1 conflict
0x91b13e91…855d
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 0x62bb20db5f…cb431e
Audit this contract →
← previous block·next block →recent activity