← previous blocknext block →recent activity
Analyzing
Block #91,096,795
16 transactions · 13 stateful · 2026-07-28 15:44:54 UTC
Parallelism
56/100
Blocked
54%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,096,795 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w19w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xce06a0f7…efef
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0x5bc8d14a…1aa9
0x34b655…2a6f
8 touches
6 conflicts
0xd021073a…271b
0x34b655…2a6f
5 touches
3 conflicts
0xe3c9b04f…1db4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
21 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity