← previous blocknext block →recent activity
Analyzing
Block #98,067,140
24 transactions · 22 stateful · 2026-08-22 01:56:02 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,067,140 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w09w110w011w112w213w318w019w120w321w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4635fb46…4cfd
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x1cabcd31…ffdc
0x34b655…2a6f
4 touches
1 conflict
0x2bd1c200…56de
0x34b655…2a6f
4 touches
1 conflict
0x4cd8c9c7…e7ff
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x6bab0076…422b
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 0x4635fb46ec…434cfd
Audit this contract →
← previous block·next block →recent activity