← previous blocknext block →recent activity
Analyzing
Block #94,849,699
41 transactions · 40 stateful · 2026-08-10 18:43:02 UTC
Parallelism
90/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,849,699 · 41 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w17w235w337w038w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x198a44fd…98d2
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x05ae4d3e…3c79
0x34b655…2a6f
4 touches
1 conflict
0xef3ea046…ac4b
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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
3 conflicts on slot 0x198a44fd08…1698d2
Audit this contract →
← previous block·next block →recent activity