← previous blocknext block →recent activity
Analyzing
Block #91,012,168
16 transactions · 15 stateful · 2026-07-28 08:39:01 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,012,168 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w17w18w29w210w312w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x466a76c3…7a61
0x851145…3f07
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x1b6c23a0…723b
0x851145…3f07
6 touches
3 conflicts
0x2a628ea8…5918
0x851145…3f07
6 touches
3 conflicts
0x5af098c7…4807
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: 0x851145ea…9f3f07
3 conflicts on slot 0x466a76c332…8b7a61
Audit this contract →
← previous block·next block →recent activity