← previous blocknext block →recent activity
Analyzing
Block #99,208,923
22 transactions · 18 stateful · 2026-08-26 02:24:28 UTC
Parallelism
77/100
Blocked
28%
Avg conflicts / tx
0.23
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,208,923 · 22 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
2w03w14w28w312w418w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcb48b33f…ed16
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x5c1b956d…14d3
0x34b655…2a6f
4 touches
1 conflict
0x59a96320…7a16
0x34b655…2a6f
4 touches
1 conflict
0x945d1dbe…e1d7
0xc8689a…ee79
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
1 conflict on slot 0xbcdd58ff98…970711
Audit this contract →
← previous block·next block →recent activity