← previous blocknext block →recent activity
Analyzing
Block #92,343,267
7 transactions · 6 stateful · 2026-08-02 00:17:19 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,343,267 · 7 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
2w03w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82a9cede…66c2
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xa03c2a35…52e6
0x34b655…2a6f
4 touches
1 conflict
0x481b6dfe…ab8e
0x34b655…2a6f
3 touches
1 conflict
0x19bbf80f…0615
0x34b655…2a6f
2 touches
0 conflicts
0x1b07bcbc…cfe0
0x34b655…2a6f
2 touches
0 conflicts
0x1b2f167d…295a
0x34b655…2a6f
2 touches
0 conflicts
0x1f396cee…862f
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 0x82a9cedebc…bb66c2
Audit this contract →
← previous block·next block →recent activity