← previous blocknext block →recent activity
Analyzing
Block #91,834,617
13 transactions · 12 stateful · 2026-07-31 05:38:55 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,834,617 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w29w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfecb18c0…01ed
0x34b655…2a6f
4 touches
1 conflict
0x07b8ca28…19fe
0x34b655…2a6f
4 touches
1 conflict
0x09a90ed3…6897
0x34b655…2a6f
4 touches
1 conflict
0x2477d0da…f68e
0x34b655…2a6f
4 touches
1 conflict
0x3e4af36e…07ae
0x34b655…2a6f
4 touches
1 conflict
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x6792a7bf…49c6
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 0xfecb18c068…6e01ed
Audit this contract →
← previous block·next block →recent activity