← previous blocknext block →recent activity
Analyzing
Block #102,253,437
18 transactions · 18 stateful · 2026-09-05 18:16:24 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,253,437 · 18 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
2w03w14w26w07w18w110w214w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d7ac3b9…22f8
0x34b655…2a6f
6 touches
3 conflicts
0x4ab70ccd…2683
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x173b64af…6c43
0x34b655…2a6f
4 touches
1 conflict
0x2711a339…af76
0x34b655…2a6f
4 touches
1 conflict
0x2cc0cad9…54fe
0x34b655…2a6f
4 touches
1 conflict
0x32e1d03e…68a7
0x34b655…2a6f
4 touches
1 conflict
0x4698a60f…d7fe
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
3 conflicts on slot 0x9d7ac3b92a…7522f8
Audit this contract →
← previous block·next block →recent activity