← previous blocknext block →recent activity
Analyzing
Block #98,414,014
13 transactions · 13 stateful · 2026-08-23 07:01:57 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,414,014 · 13 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
4w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5060cdde…445d
0x34b655…2a6f
6 touches
3 conflicts
0xb4246f82…f9b2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc53799eb…d928
0x34b655…2a6f
4 touches
1 conflict
0xf3b253be…78b5
0x34b655…2a6f
4 touches
1 conflict
0xb14b376f…a2eb
0x34b655…2a6f
4 touches
1 conflict
0xa020506f…7c60
0x34b655…2a6f
4 touches
1 conflict
0x3129b531…9db1
0x754704…b603
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
3 conflicts on slot 0x5060cdde9e…d4445d
Audit this contract →
← previous block·next block →recent activity