← previous blocknext block →recent activity
Analyzing
Block #103,214,243
21 transactions · 20 stateful · 2026-09-09 03:09:51 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,214,243 · 21 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
3w05w113w214w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48cb599a…c21c
0x34b655…2a6f
6 touches
3 conflicts
0xd9722304…6ed0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb3339b9d…eeff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcc844ab5…4c6d
0x34b655…2a6f
4 touches
1 conflict
0x3ba7edbb…80e6
0x34ae4d…3fc5
2 touches
0 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
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
3 conflicts on slot 0x48cb599a7b…38c21c
Audit this contract →
← previous block·next block →recent activity