← previous blocknext block →recent activity
Analyzing
Block #100,738,352
14 transactions · 12 stateful · 2026-08-31 10:59:38 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,738,352 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfc8cc8e1…85f1
0x34b655…2a6f
3 touches
1 conflict
0xb452f445…a2c2
0x34b655…2a6f
3 touches
1 conflict
0x62811193…1867
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…186d
0x34ae4d…3fc5
2 touches
0 conflicts
0x80caf0f7…f2de
0x34ae4d…3fc5
2 touches
0 conflicts
0xb0dd578f…873c
0x34ae4d…3fc5
2 touches
0 conflicts
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
1 conflict on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity