← previous blocknext block →recent activity
Analyzing
Block #102,418,409
43 transactions · 29 stateful · 2026-09-06 08:12:16 UTC
Parallelism
91/100
Blocked
31%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,418,409 · 43 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
3w09w010w012w013w115w117w018w221w122w129w036w337w138w141w042w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b446d2…2006
0x34b655…2a6f
6 touches
3 conflicts
0xa4c96d4b…9420
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x810f1cd4…5879
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
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 0xb7b446d20b…4f2006
Audit this contract →
← previous block·next block →recent activity