← previous blocknext block →recent activity
Analyzing
Block #91,294,349
16 transactions · 16 stateful · 2026-07-29 08:19:35 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,294,349 · 16 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
0w03w17w08w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb6225cbd…94e1
0x34b655…2a6f
4 touches
1 conflict
0xba6f6560…e7ea
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x1ee6a8c8…026f
0x34b655…2a6f
4 touches
1 conflict
0x7729d2c9…8c22
0x34b655…2a6f
4 touches
1 conflict
0x7729d2c9…8c23
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 0x7e5ea60ab2…b0c4ab
Audit this contract →
← previous block·next block →recent activity