← previous blocknext block →recent activity
Analyzing
Block #92,202,240
6 transactions · 5 stateful · 2026-08-01 12:28:03 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,202,240 · 6 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
1w02w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x2979e2dd…335e
0x34b655…2a6f
4 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x19e1da6e…4a72
0x34b655…2a6f
2 touches
0 conflicts
0x2bf93390…3c93
0x34b655…2a6f
2 touches
0 conflicts
0x38728bec…1de9
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity