← previous blocknext block →recent activity
Analyzing
Block #99,483,892
20 transactions · 18 stateful · 2026-08-27 01:28:39 UTC
Parallelism
85/100
Blocked
28%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,483,892 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w012w113w214w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ee34d1…30f8
0x34b655…2a6f
6 touches
3 conflicts
0x8f2a8b46…fc85
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf4b2a427…0234
0x34b655…2a6f
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x5c455afd…ce06
0x34b655…2a6f
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
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
3 conflicts on slot 0x69ee34d107…a730f8
Audit this contract →
← previous block·next block →recent activity