← previous blocknext block →recent activity
Analyzing
Block #91,996,373
16 transactions · 13 stateful · 2026-07-31 19:12:41 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,996,373 · 16 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
2w03w18w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f4e7625…aba5
0x34b655…2a6f
4 touches
1 conflict
0xb7fb66e8…4f94
0x34b655…2a6f
4 touches
1 conflict
0xd793c15e…7dba
0x34b655…2a6f
4 touches
1 conflict
0xfcecce2a…149c
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x7ebbbc57…fb01
0x065c9d…c394
2 touches
0 conflicts
0x9f365cc0…cc96
0x065c9d…c394
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 0x6f4e76253a…03aba5
Audit this contract →
← previous block·next block →recent activity