← previous blocknext block →recent activity
Analyzing
Block #100,588,934
16 transactions · 14 stateful · 2026-08-30 22:28:01 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,588,934 · 16 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
1w02w15w06w08w19w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76622fb2…4f08
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd2dfd9bc…3eec
0x34b655…2a6f
4 touches
1 conflict
0xd775d2ad…c71e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x39977254…07b1
0x2b46c0…1669
2 touches
0 conflicts
0x5a409e7f…09b6
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 0x76622fb2e3…024f08
Audit this contract →
← previous block·next block →recent activity