← previous blocknext block →recent activity
Analyzing
Block #105,618,687
29 transactions · 26 stateful · 2026-09-17 13:35:24 UTC
Parallelism
83/100
Blocked
46%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,618,687 · 29 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
1w02w16w07w115w116w217w118w219w320w421w022w323w127w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62f61155…0135
0x34b655…2a6f
10 touches
10 conflicts
0xdb1e37cb…90c9
0x34b655…2a6f
10 touches
10 conflicts
0x5fde4971…aac9
0x34b655…2a6f
6 touches
3 conflicts
0xca608d0c…f23b
0x34b655…2a6f
6 touches
3 conflicts
0xd5212adb…d363
0x34b655…2a6f
6 touches
3 conflicts
0x42daad7f…630b
0xa6afd3…d132
6 touches
3 conflicts
0xfac61869…a55e
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
10 conflicts on slot 0x62f61155a1…a60135
Audit this contract →
← previous block·next block →recent activity