← previous blocknext block →recent activity
Analyzing
Block #98,071,884
22 transactions · 20 stateful · 2026-08-22 02:19:55 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,071,884 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w07w18w110w213w314w417w118w521w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86d49fa1…0dfd
0x34b655…2a6f
6 touches
3 conflicts
0x9ae859db…2d84
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x2a181dd8…1b63
0x34b655…2a6f
4 touches
1 conflict
0x3151b440…d0aa
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
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 0x86d49fa11d…b20dfd
Audit this contract →
← previous block·next block →recent activity