← previous blocknext block →recent activity
Analyzing
Block #101,682,396
15 transactions · 13 stateful · 2026-09-03 18:09:49 UTC
Parallelism
73/100
Blocked
46%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,682,396 · 15 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
3w04w16w17w08w110w211w313w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec4c6536…f8e8
0x34b655…2a6f
4 touches
1 conflict
0x5e3090f2…00cc
0x34b655…2a6f
4 touches
1 conflict
0x635d0f25…4d22
0x34b655…2a6f
4 touches
1 conflict
0xb027a906…65a2
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
1 conflict on slot 0xec4c6536c5…b1f8e8
Audit this contract →
← previous block·next block →recent activity