← previous blocknext block →recent activity
Analyzing
Block #98,492,378
64 transactions · 46 stateful · 2026-08-23 13:36:33 UTC
Parallelism
80/100
Blocked
61%
Avg conflicts / tx
1.7
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,492,378 · 64 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w08w114w215w317w018w119w223w024w125w429w030w131w232w333w434w535w636w737w838w939w1040w1144w247w149w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 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: 0xbb3f3cb7…74e046
78 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity