← previous blocknext block →recent activity
Analyzing
Block #98,427,129
19 transactions · 16 stateful · 2026-08-23 08:07:56 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,427,129 · 19 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
1w02w15w06w110w111w213w016w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda976e7f…128a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x803bf237…2cc1
0x34b655…2a6f
4 touches
1 conflict
0x82f46d1e…1831
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x403a4649…d8be
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
3 conflicts on slot 0xda976e7f2f…0e128a
Audit this contract →
← previous block·next block →recent activity