← previous blocknext block →recent activity
Analyzing
Block #98,990,174
7 transactions · 7 stateful · 2026-08-25 07:57:12 UTC
Parallelism
43/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,990,174 · 7 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
2w03w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe108b282…58b3
0x34b655…2a6f
4 touches
1 conflict
0x20b94f7c…2a9b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x385965ea…a4b7
0x34b655…2a6f
2 touches
0 conflicts
0x3bca67b5…842d
0x34b655…2a6f
2 touches
0 conflicts
0x5b50b454…614a
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
1 conflict on slot 0xe108b28272…6558b3
Audit this contract →
← previous block·next block →recent activity