← previous blocknext block →recent activity
Analyzing
Block #98,064,789
21 transactions · 15 stateful · 2026-08-22 01:44:12 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,064,789 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w310w011w113w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x6f4bc4eb…3351
0x34b655…2a6f
4 touches
1 conflict
0x2ab9baf1…a394
0x34b655…2a6f
3 touches
1 conflict
0x86d49fa1…0dfd
0x34b655…2a6f
3 touches
1 conflict
0xcfb0bc18…2e85
0x34b655…2a6f
3 touches
1 conflict
0xb99398a0…919f
0x34b655…2a6f
3 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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity