← previous blocknext block →recent activity
Analyzing
Block #105,576,724
16 transactions · 13 stateful · 2026-09-17 10:04:10 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,576,724 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w19w010w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54060017…c0c6
0xe7cd86…c82d
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0161566e…abb2
0xa6afd3…d132
4 touches
1 conflict
0xc45e4fb5…7cc3
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0000
0xacf82e…3500
4 touches
1 conflict
0x00000000…0002
0xacf82e…3500
4 touches
1 conflict
0xb96082a1…61a5
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
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: 0xe7cd86e1…0fc82d
1 conflict on slot 0x540600176b…aac0c6
Audit this contract →
← previous block·next block →recent activity