← previous blocknext block →recent activity
Analyzing
Block #101,324,486
15 transactions · 15 stateful · 2026-09-02 12:09:04 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,324,486 · 15 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
1w04w05w16w17w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c6da4eb…03eb
0x34b655…2a6f
4 touches
1 conflict
0x0aa9b1c4…4c76
0x34b655…2a6f
4 touches
1 conflict
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xff324643…41db
0x34b655…2a6f
4 touches
1 conflict
0x2d02f869…1f83
0x34b655…2a6f
2 touches
0 conflicts
0x336486a4…20bd
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 0x1c6da4eb95…b903eb
Audit this contract →
← previous block·next block →recent activity