← previous blocknext block →recent activity
Analyzing
Block #100,791,157
19 transactions · 16 stateful · 2026-08-31 15:25:27 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,791,157 · 19 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
7w013w014w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc9915b5…542c
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xccac5761…675b
0x34b655…2a6f
4 touches
1 conflict
0xd6c976a1…1d47
0x34b655…2a6f
4 touches
1 conflict
0xd6c976a1…1d48
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
1 conflict on slot 0xdc9915b513…2b542c
Audit this contract →
← previous block·next block →recent activity