← previous blocknext block →recent activity
Analyzing
Block #98,427,789
14 transactions · 14 stateful · 2026-08-23 08:11:15 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,427,789 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f5707c2…cda2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcadd9a74…8bb7
0x34b655…2a6f
4 touches
1 conflict
0x5e8f1bea…875b
0x34b655…2a6f
4 touches
1 conflict
0x2101bec4…84b9
0x34b655…2a6f
2 touches
0 conflicts
0x232df012…c608
0x34b655…2a6f
2 touches
0 conflicts
0x241c87c4…99b5
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 0x2f5707c2b3…3ccda2
Audit this contract →
← previous block·next block →recent activity