← previous blocknext block →recent activity
Analyzing
Block #92,071,610
16 transactions · 13 stateful · 2026-08-01 01:31:05 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,071,610 · 16 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
3w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d3930d3…c9b8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x38f3c47d…7992
0x34b655…2a6f
4 touches
1 conflict
0xe28e89d1…0cf0
0x34b655…2a6f
4 touches
1 conflict
0x1e737223…2278
0x34b655…2a6f
2 touches
0 conflicts
0x1f6f7945…5ce6
0x34b655…2a6f
2 touches
0 conflicts
0x2a949bb2…8769
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 0x2d3930d3fc…56c9b8
Audit this contract →
← previous block·next block →recent activity