← previous blocknext block →recent activity
Analyzing
Block #99,854,468
17 transactions · 17 stateful · 2026-08-28 08:46:57 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,854,468 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w07w18w210w311w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8b6d32…6601
0x34b655…2a6f
8 touches
6 conflicts
0xd388875c…6257
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x184a9b09…c825
0x34b655…2a6f
4 touches
1 conflict
0x3cc3cee1…372a
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
6 conflicts on slot 0xcc8b6d3248…e46601
Audit this contract →
← previous block·next block →recent activity