← previous blocknext block →recent activity
Analyzing
Block #98,384,895
17 transactions · 17 stateful · 2026-08-23 04:35:27 UTC
Parallelism
82/100
Blocked
24%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,384,895 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w215w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5934b407…e058
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xf9d7a5ab…d418
0x34b655…2a6f
4 touches
1 conflict
0x3de537b0…23ed
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf95f86cd…e927
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
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
3 conflicts on slot 0x5934b407c2…7fe058
Audit this contract →
← previous block·next block →recent activity