← previous blocknext block →recent activity
Analyzing
Block #98,275,244
16 transactions · 14 stateful · 2026-08-22 19:23:45 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,275,244 · 16 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
2w06w09w010w112w113w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0xf8cb14ea…b0eb
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb20094ed…0fef
0x34b655…2a6f
4 touches
1 conflict
0xabb9f292…17a3
0x34b655…2a6f
4 touches
1 conflict
0x832cf0ec…3457
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 0x3e6302c867…b164f5
Audit this contract →
← previous block·next block →recent activity