← previous blocknext block →recent activity
Analyzing
Block #99,447,824
28 transactions · 19 stateful · 2026-08-26 22:27:01 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,447,824 · 28 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
1w02w03w16w19w017w018w122w225w126w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x801a6e57…d85c
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity