← previous blocknext block →recent activity
Analyzing
Block #105,933,415
26 transactions · 23 stateful · 2026-09-18 16:01:47 UTC
Parallelism
81/100
Blocked
65%
Avg conflicts / tx
1.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,933,415 · 26 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
1w02w13w24w36w09w410w011w112w013w214w215w316w017w118w219w323w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x162f39bf…d831
0x6f6493…b480
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
10 touches
10 conflicts
0x14af78bb…aed7
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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: 0x6f6493e3…08b480
10 conflicts on slot 0x162f39bfbc…19d831
Audit this contract →
← previous block·next block →recent activity