← previous blocknext block →recent activity
Analyzing
Block #100,793,794
19 transactions · 16 stateful · 2026-08-31 15:38:43 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,793,794 · 19 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
1w03w14w06w19w010w012w113w215w016w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0xbae3502c…9836
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x9482a067…eba9
0x34b655…2a6f
4 touches
1 conflict
0xa5ab7b8a…c97b
0x34b655…2a6f
4 touches
1 conflict
0xaa48195d…ffee
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
3 conflicts on slot 0xab981df1f6…082941
Audit this contract →
← previous block·next block →recent activity