← previous blocknext block →recent activity
Analyzing
Block #100,734,861
17 transactions · 15 stateful · 2026-08-31 10:42:05 UTC
Parallelism
59/100
Blocked
40%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,734,861 · 17 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
2w03w14w27w09w011w312w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08e8f2c9…a11a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0xbe49f28d…ede1
0x34b655…2a6f
4 touches
1 conflict
0xe9457301…83cd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0x08e8f2c94d…1ca11a
Audit this contract →
← previous block·next block →recent activity