← previous blocknext block →recent activity
Analyzing
Block #100,792,195
16 transactions · 15 stateful · 2026-08-31 15:30:40 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,792,195 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w411w012w113w214w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x79347b24…9fba
0x34b655…2a6f
6 touches
3 conflicts
0xf4497fd3…6ff0
0x34b655…2a6f
4 touches
1 conflict
0x4bcb5304…7776
0x34b655…2a6f
4 touches
1 conflict
0x8311570f…5321
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity