← previous blocknext block →recent activity
Analyzing
Block #94,060,190
15 transactions · 13 stateful · 2026-08-08 00:14:36 UTC
Parallelism
60/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,060,190 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w37w08w19w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x539ac47f…eb6f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x210cc072…696f
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x3d6a3e2e…abb3
0x34b655…2a6f
4 touches
1 conflict
0x7fa44fe8…484e
0x34b655…2a6f
2 touches
0 conflicts
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
6 conflicts on slot 0x539ac47ff9…e9eb6f
Audit this contract →
← previous block·next block →recent activity