← previous blocknext block →recent activity
Analyzing
Block #98,074,114
18 transactions · 14 stateful · 2026-08-22 02:31:08 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,074,114 · 18 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
3w04w06w08w19w210w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd6e6faa…f569
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x03a6363b…ad2b
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x04d97ccd…20d1
0x34b655…2a6f
4 touches
1 conflict
0x5c658cea…f482
0x34b655…2a6f
4 touches
1 conflict
0x60b3b7b2…1af3
0x34b655…2a6f
4 touches
1 conflict
0x61818eda…690c
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 0xcd6e6faa6e…a5f569
Audit this contract →
← previous block·next block →recent activity