← previous blocknext block →recent activity
Analyzing
Block #100,079,986
18 transactions · 17 stateful · 2026-08-29 03:43:01 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
1.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,079,986 · 18 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
4w05w17w28w39w010w311w413w514w616w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b43dd7d…7f99
0x34b655…2a6f
12 touches
15 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
12 touches
15 conflicts
0xc8328065…611a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x67a56c8b…f955
0x34b655…2a6f
6 touches
3 conflicts
0x038b9243…553d
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
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
15 conflicts on slot 0x2b43dd7d55…f37f99
Audit this contract →
← previous block·next block →recent activity