← previous blocknext block →recent activity
Analyzing
Block #92,635,705
12 transactions · 12 stateful · 2026-08-03 00:48:05 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,635,705 · 12 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
2w03w04w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe58009e8…fe3f
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0xc03846bb…73b3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0bee8017…c90a
0x34b655…2a6f
4 touches
1 conflict
0x0c612d13…2829
0x34b655…2a6f
4 touches
1 conflict
0x10aa6a2c…5cd8
0x34b655…2a6f
4 touches
1 conflict
0x1c8356f1…c7a2
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 0xe58009e820…f6fe3f
Audit this contract →
← previous block·next block →recent activity