← previous blocknext block →recent activity
Analyzing
Block #98,101,179
17 transactions · 17 stateful · 2026-08-22 04:47:20 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,101,179 · 17 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
2w04w05w17w18w09w111w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca23620f…f126
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0fe9ce4d…1d44
0x34b655…2a6f
4 touches
1 conflict
0x70f537e8…399b
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x350d32fc…f659
0x34b655…2a6f
2 touches
0 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xca23620f1e…acf126
Audit this contract →
← previous block·next block →recent activity