← previous blocknext block →recent activity
Analyzing
Block #92,000,172
14 transactions · 11 stateful · 2026-07-31 19:31:47 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,000,172 · 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
1w02w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xe05f88c7…0b79
0x065c9d…c394
3 touches
1 conflict
0x2e7a0c1d…caaf
0x34b655…2a6f
2 touches
0 conflicts
0x433ec3a1…a1e8
0x34b655…2a6f
2 touches
0 conflicts
0x51134e2a…e079
0x34b655…2a6f
2 touches
0 conflicts
0x12530975…a089
0x3bd359…433a
2 touches
0 conflicts
0xc7ea2751…3347
0x3bd359…433a
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 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity