← previous blocknext block →recent activity
Analyzing
Block #91,998,105
21 transactions · 16 stateful · 2026-07-31 19:21:24 UTC
Parallelism
90/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,998,105 · 21 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
4w06w17w010w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1b40f29…9b9d
0x34b655…2a6f
4 touches
1 conflict
0x4af8f8d2…0850
0x34b655…2a6f
4 touches
1 conflict
0x514e8c17…48c0
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x714420ba…96c5
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xb7d187eb…68c0
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 0xd1b40f2924…ae9b9d
Audit this contract →
← previous block·next block →recent activity