← previous blocknext block →recent activity
Analyzing
Block #99,870,076
16 transactions · 16 stateful · 2026-08-28 10:05:44 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,870,076 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w312w013w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7ad475a…0e41
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x96ed54e2…04ed
0x34b655…2a6f
4 touches
1 conflict
0xa9a49465…0424
0x34b655…2a6f
4 touches
1 conflict
0xf8f1e808…a4fd
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 0xe7ad475a4a…4e0e41
Audit this contract →
← previous block·next block →recent activity