← previous blocknext block →recent activity
Analyzing
Block #98,148,654
19 transactions · 16 stateful · 2026-08-22 08:46:54 UTC
Parallelism
74/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,148,654 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w08w110w211w314w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9efe106e…72d2
0x34b655…2a6f
8 touches
6 conflicts
0x61ca6437…2142
0x34b655…2a6f
6 touches
3 conflicts
0xc6d445ec…8564
0x34b655…2a6f
6 touches
3 conflicts
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0x04994ed2…9032
0x34b655…2a6f
4 touches
1 conflict
0x2b3c1546…85d1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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
6 conflicts on slot 0x9efe106ebb…ad72d2
Audit this contract →
← previous block·next block →recent activity