← previous blocknext block →recent activity
Analyzing
Block #91,763,023
14 transactions · 13 stateful · 2026-07-30 23:38:46 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,763,023 · 14 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
1w02w03w05w17w09w110w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x875dd001…c5d9
0x40c49f…2af0
4 touches
1 conflict
0x3560a56c…d95d
0x34b655…2a6f
4 touches
1 conflict
0x45ef9175…5ab2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbe54b7d5…1bda
0x34b655…2a6f
4 touches
1 conflict
0xcdd95ca7…a9c8
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: 0x40c49f17…d22af0
1 conflict on slot 0x875dd001e1…6dc5d9
Audit this contract →
← previous block·next block →recent activity