← previous blocknext block →recent activity
Analyzing
Block #92,359,538
8 transactions · 8 stateful · 2026-08-02 01:39:09 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,359,538 · 8 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x262d5015…771b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xbb9cf762…9f62
0x34b655…2a6f
3 touches
1 conflict
0x04994ed2…9032
0x34b655…2a6f
2 touches
0 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x4abfb389…18f4
0x34b655…2a6f
2 touches
0 conflicts
0x4e8c4408…d37a
0x34b655…2a6f
2 touches
0 conflicts
0x4e8c4408…d37b
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 0x262d50150d…26771b
Audit this contract →
← previous block·next block →recent activity