← previous blocknext block →recent activity
Analyzing
Block #98,474,512
14 transactions · 14 stateful · 2026-08-23 12:06:40 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,474,512 · 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
1w03w04w15w18w09w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0xec5e8745…3135
0x8964d7…10f8
4 touches
1 conflict
0xec5e8745…3136
0x8964d7…10f8
4 touches
1 conflict
0xec5e8745…3139
0x8964d7…10f8
4 touches
1 conflict
0xec5e8745…313a
0x8964d7…10f8
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 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity