← previous blocknext block →recent activity
Analyzing
Block #100,119,439
15 transactions · 15 stateful · 2026-08-29 07:01:41 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,119,439 · 15 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
4w05w16w07w08w19w211w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc81faf7…1417
0x34b655…2a6f
6 touches
3 conflicts
0xccfc5788…0819
0x34b655…2a6f
6 touches
3 conflicts
0x334209f4…aace
0x34b655…2a6f
4 touches
1 conflict
0x47c2ce68…aa59
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x8dad7932…7029
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 0xfc81faf76e…be1417
Audit this contract →
← previous block·next block →recent activity