← previous blocknext block →recent activity
Analyzing
Block #99,626,575
21 transactions · 19 stateful · 2026-08-27 13:33:52 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,626,575 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w18w010w111w113w114w216w318w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd08db6ee…a943
0x40c49f…2af0
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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: 0x40c49f17…d22af0
3 conflicts on slot 0xd08db6eea8…34a943
Audit this contract →
← previous block·next block →recent activity