← previous blocknext block →recent activity
Analyzing
Block #105,672,433
19 transactions · 18 stateful · 2026-09-17 18:05:58 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,672,433 · 19 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
2w03w14w011w112w213w314w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb839a1e8…22b3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x451a771d…2a72
0x34b655…2a6f
8 touches
6 conflicts
0xb5f5f775…010b
0x34b655…2a6f
8 touches
6 conflicts
0x07d94be1…7fa8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x5312402f…0d71
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xb839a1e822…9422b3
Audit this contract →
← previous block·next block →recent activity