← previous blocknext block →recent activity
Analyzing
Block #101,841,499
25 transactions · 22 stateful · 2026-09-04 07:30:04 UTC
Parallelism
84/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,841,499 · 25 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
3w04w05w18w010w111w213w120w021w124w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0dd3bdfb…7537
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x9db468f2…805a
0x34b655…2a6f
4 touches
1 conflict
0xaafad371…9bbf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity