← previous blocknext block →recent activity
Analyzing
Block #102,061,256
19 transactions · 19 stateful · 2026-09-05 02:02:13 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,061,256 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w111w012w213w314w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x708011e5…df12
0x34b655…2a6f
4 touches
1 conflict
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x2eb15031…f48d
0x34b655…2a6f
4 touches
1 conflict
0x1dc71894…1884
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xaf199a64…16ed
0x34b655…2a6f
4 touches
1 conflict
0xb637bebe…4cf9
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x708011e56c…47df12
Audit this contract →
← previous block·next block →recent activity