← previous blocknext block →recent activity
Analyzing
Block #100,147,092
14 transactions · 14 stateful · 2026-08-29 09:21:02 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,147,092 · 14 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
4w010w111w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x191e0467…70e5
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xe26c4e53…94c3
0x34b655…2a6f
4 touches
1 conflict
0xe26c4e53…94c2
0x34b655…2a6f
4 touches
1 conflict
0x8b87ece6…3353
0x34b655…2a6f
4 touches
1 conflict
0xc7f6eab9…9e9f
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity