← previous blocknext block →recent activity
Analyzing
Block #105,470,723
19 transactions · 18 stateful · 2026-09-17 01:10:42 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,470,723 · 19 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
1w02w19w113w014w115w216w317w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x576c36d1…f482
0x34b655…2a6f
6 touches
3 conflicts
0x713bab50…13ae
0x065c9d…c394
5 touches
3 conflicts
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
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 0x576c36d16e…50f482
Audit this contract →
← previous block·next block →recent activity