← previous blocknext block →recent activity
Analyzing
Block #100,725,594
11 transactions · 10 stateful · 2026-08-31 09:55:28 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,725,594 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb050f628…5ad6
0x34b655…2a6f
4 touches
1 conflict
0xe26c4e53…94c2
0x34b655…2a6f
4 touches
1 conflict
0x0f41eeca…9d2a
0x34b655…2a6f
4 touches
1 conflict
0x2d7bc277…e916
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x33b5035a…d1c6
0x34b655…2a6f
4 touches
1 conflict
0x1560ba30…9093
0x34b655…2a6f
4 touches
1 conflict
0x3ee8b564…4c49
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 0xb050f628d8…065ad6
Audit this contract →
← previous block·next block →recent activity