← previous blocknext block →recent activity
Analyzing
Block #99,504,479
12 transactions · 12 stateful · 2026-08-27 03:12:17 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,504,479 · 12 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
4w08w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86d26761…7ed4
0x34b655…2a6f
4 touches
1 conflict
0x605e358e…dc99
0x34b655…2a6f
4 touches
1 conflict
0x63a6dacd…54a1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xebaee02b…6106
0x34b655…2a6f
4 touches
1 conflict
0x19b34ad0…1b7b
0x34b655…2a6f
4 touches
1 conflict
0x19b34ad0…1b7c
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
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 0x86d2676147…9a7ed4
Audit this contract →
← previous block·next block →recent activity