← previous blocknext block →recent activity
Analyzing
Block #92,470,198
5 transactions · 3 stateful · 2026-08-02 10:55:38 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,470,198 · 5 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x248e43aa…7287
0x34b655…2a6f
4 touches
1 conflict
0x816c7d6d…98ea
0x34b655…2a6f
4 touches
1 conflict
0x816c7d6d…98eb
0x34b655…2a6f
4 touches
1 conflict
0x064a19b6…3f1d
0x34b655…2a6f
2 touches
0 conflicts
0x1f67cbca…6ffa
0x34b655…2a6f
2 touches
0 conflicts
0x2fb55b69…276d
0x34b655…2a6f
2 touches
0 conflicts
0x3adf6cd7…6f2c
0x34b655…2a6f
2 touches
0 conflicts
0x7462b8f2…6312
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 0x248e43aaac…e67287
Audit this contract →
← previous block·next block →recent activity