← previous blocknext block →recent activity
Analyzing
Block #98,444,393
14 transactions · 12 stateful · 2026-08-23 09:34:47 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,444,393 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x420d4258…a333
0x34b655…2a6f
4 touches
1 conflict
0x3e7cbb84…c91a
0x34b655…2a6f
3 touches
1 conflict
0x0b4267f7…96c0
0x34b655…2a6f
2 touches
0 conflicts
0x34dd7a37…260e
0x34b655…2a6f
2 touches
0 conflicts
0x55e61553…6c44
0x34b655…2a6f
2 touches
0 conflicts
0x57330c5d…9973
0x34b655…2a6f
2 touches
0 conflicts
0x6a2ca7be…18a8
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity