← previous blocknext block →recent activity
Analyzing
Block #98,100,315
31 transactions · 28 stateful · 2026-08-22 04:42:59 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,100,315 · 31 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
1w02w03w15w06w08w29w010w115w016w118w219w320w422w123w224w325w529w530w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cd6078c…7e9b
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0x9a100e05…c541
0x34b655…2a6f
6 touches
3 conflicts
0xb1856468…e84f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
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
10 conflicts on slot 0x6cd6078c74…697e9b
Audit this contract →
← previous block·next block →recent activity