← previous blocknext block →recent activity
Analyzing
Block #105,618,571
16 transactions · 14 stateful · 2026-09-17 13:34:49 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,618,571 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x72b3dc81…d09e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x178a61ad…4958
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xa0720dfe…2d4d
0x34b655…2a6f
4 touches
1 conflict
0x56e0d685…c960
0x34b655…2a6f
2 touches
0 conflicts
0x744a7694…d2c0
0x34b655…2a6f
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 0x6ca0994e1e…7002ef
Audit this contract →
← previous block·next block →recent activity