← previous blocknext block →recent activity
Analyzing
Block #100,139,596
21 transactions · 17 stateful · 2026-08-29 08:43:18 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,139,596 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w09w010w113w014w217w318w419w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d7bbd81…7cc6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd5c98027…9fd9
0x34b655…2a6f
6 touches
3 conflicts
0xe7297800…65cf
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x50c61506…343f
0x34b655…2a6f
6 touches
3 conflicts
0xc20bd100…8b0e
0x2b46c0…1669
4 touches
1 conflict
0x42522e76…2592
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
6 conflicts on slot 0x1d7bbd81bb…287cc6
Audit this contract →
← previous block·next block →recent activity