← previous blocknext block →recent activity
Analyzing
Block #100,160,538
12 transactions · 12 stateful · 2026-08-29 10:28:44 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,160,538 · 12 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
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7ef0c17…df1d
0x34b655…2a6f
4 touches
1 conflict
0x24bc7f29…cfad
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb44
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb45
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb8f61e91…35e7
0x34b655…2a6f
4 touches
1 conflict
0xd7d3e7dd…2bf3
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 0xf7ef0c17cc…79df1d
Audit this contract →
← previous block·next block →recent activity