← previous blocknext block →recent activity
Analyzing
Block #100,737,536
29 transactions · 22 stateful · 2026-08-31 10:55:32 UTC
Parallelism
86/100
Blocked
41%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,737,536 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w27w08w19w210w314w016w122w123w227w028w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
6 touches
3 conflicts
0x90b1f042…5833
0x851145…3f07
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd9722304…6ed0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x5f0a01c3…8269
0x851145…3f07
4 touches
1 conflict
0x87d39100…7270
0x851145…3f07
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
3 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity