← previous blocknext block →recent activity
Analyzing
Block #92,432,475
13 transactions · 11 stateful · 2026-08-02 07:45:56 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,432,475 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w210w011w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x001d91db…8b3c
0x34b655…2a6f
4 touches
1 conflict
0x171352be…07ab
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x233f83e8…a074
0x34b655…2a6f
4 touches
1 conflict
0x2f92e43a…44c4
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x36b7c9c3…03bd
0x34b655…2a6f
4 touches
1 conflict
0x5d7e0e69…e6d1
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
1 conflict on slot 0x001d91db5c…348b3c
Audit this contract →
← previous block·next block →recent activity