← previous blocknext block →recent activity
Analyzing
Block #100,617,252
25 transactions · 20 stateful · 2026-08-31 00:50:29 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,617,252 · 25 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
1w02w15w09w010w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82553353…0c9b
0x34b655…2a6f
4 touches
1 conflict
0x0476d77b…a514
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x29cd05f5…390c
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x5e8223c2…c242
0x34b655…2a6f
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
1 conflict on slot 0x82553353c2…7f0c9b
Audit this contract →
← previous block·next block →recent activity