← previous blocknext block →recent activity
Analyzing
Block #92,483,247
14 transactions · 14 stateful · 2026-08-02 12:01:20 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,483,247 · 14 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
4w06w07w19w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68a2902c…b23f
0x34b655…2a6f
4 touches
1 conflict
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0x2a89109e…ce36
0x40c49f…2af0
4 touches
1 conflict
0x1fd19887…8e0e
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x3fff7ccd…5a48
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 0x68a2902c52…e3b23f
Audit this contract →
← previous block·next block →recent activity