← previous blocknext block →recent activity
Analyzing
Block #98,743,342
28 transactions · 24 stateful · 2026-08-24 11:15:02 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,743,342 · 28 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
2w03w15w16w29w010w111w113w018w120w223w024w125w326w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xead15497…1dbe
0x34b655…2a6f
6 touches
3 conflicts
0x47b807a2…3307
0x065c9d…c394
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x81955a0a…29ee
0x340143…768f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x4d1e3e31…edf8
0x3bd359…433a
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
3 conflicts on slot 0xead15497a3…971dbe
Audit this contract →
← previous block·next block →recent activity