← previous blocknext block →recent activity
Analyzing
Block #100,604,053
38 transactions · 31 stateful · 2026-08-30 23:44:05 UTC
Parallelism
87/100
Blocked
52%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,604,053 · 38 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w06w17w19w012w013w114w115w216w017w018w019w220w123w125w226w327w128w329w130w235w237w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36918c55…8424
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
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 0x36918c5535…2c8424
Audit this contract →
← previous block·next block →recent activity