← previous blocknext block →recent activity
Analyzing
Block #101,924,489
12 transactions · 10 stateful · 2026-09-04 14:28:53 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,924,489 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b4f173c…94e6
0x34b655…2a6f
4 touches
1 conflict
0x21adef83…f2b7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcb7c4d5f…b7af
0x34b655…2a6f
4 touches
1 conflict
0xdf146090…28f8
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
2 touches
0 conflicts
0x533967c4…cf36
0x34b655…2a6f
2 touches
0 conflicts
0x5f3e4946…a474
0x34b655…2a6f
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
1 conflict on slot 0x9b4f173cee…8c94e6
Audit this contract →
← previous block·next block →recent activity