← previous blocknext block →recent activity
Analyzing
Block #98,672,693
24 transactions · 23 stateful · 2026-08-24 05:15:16 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,672,693 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w08w19w210w312w113w317w220w021w122w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0xcf37f77e…a027
0x34b655…2a6f
6 touches
3 conflicts
0x420d4258…a333
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x74c615ff…15c0
0x34b655…2a6f
5 touches
3 conflicts
0x7aad02c6…b979
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity