← previous blocknext block →recent activity
Analyzing
Block #98,652,857
18 transactions · 16 stateful · 2026-08-24 03:31:47 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,652,857 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x386d08f4…5a01
0x34b655…2a6f
4 touches
1 conflict
0x2cef1eff…9f14
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0949e4a6…8f2f
0x34b655…2a6f
2 touches
0 conflicts
0x15e1f6e3…f38c
0x34b655…2a6f
2 touches
0 conflicts
0x2bea5ce8…3c07
0x34b655…2a6f
2 touches
0 conflicts
0x2c539d94…b63a
0x34b655…2a6f
2 touches
0 conflicts
0x2e0edc98…9765
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 0x386d08f44a…fc5a01
Audit this contract →
← previous block·next block →recent activity