← previous blocknext block →recent activity
Analyzing
Block #98,755,365
7 transactions · 7 stateful · 2026-08-24 12:15:37 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,755,365 · 7 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
2w03w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x324ad7e8…b138
0x34b655…2a6f
2 touches
0 conflicts
0x3dad3b45…8edb
0x34b655…2a6f
2 touches
0 conflicts
0x5491840e…f1a0
0x34b655…2a6f
2 touches
0 conflicts
0x63726607…4e47
0x34b655…2a6f
2 touches
0 conflicts
0x7c27dee3…a2e0
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity