← previous blocknext block →recent activity
Analyzing
Block #98,427,208
39 transactions · 33 stateful · 2026-08-23 08:08:20 UTC
Parallelism
77/100
Blocked
67%
Avg conflicts / tx
1.49
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,427,208 · 39 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w06w17w28w310w412w013w114w415w516w617w125w126w727w530w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x11258774…9892
0x2a68ba…90c5
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xd6fc1712…971e
0x065c9d…c394
7 touches
6 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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity