← previous blocknext block →recent activity
Analyzing
Block #98,081,832
22 transactions · 21 stateful · 2026-08-22 03:09:59 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,081,832 · 22 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
1w02w05w06w17w111w113w214w215w016w219w120w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ee8b564…4c49
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x5db0ca44…afdf
0x34b655…2a6f
4 touches
1 conflict
0x5fadfaca…5032
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0x3ee8b5644d…f04c49
Audit this contract →
← previous block·next block →recent activity