← previous blocknext block →recent activity
Analyzing
Block #92,564,077
10 transactions · 10 stateful · 2026-08-02 18:47:49 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,564,077 · 10 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
1w02w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6edabb88…c874
0x34b655…2a6f
4 touches
1 conflict
0x9ad82ccb…b08c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x4dc18bef…59da
0x34b655…2a6f
2 touches
0 conflicts
0x5a812049…d85d
0x34b655…2a6f
2 touches
0 conflicts
0x6416a9d2…489a
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 0x6edabb8894…a2c874
Audit this contract →
← previous block·next block →recent activity