← previous blocknext block →recent activity
Analyzing
Block #102,051,172
27 transactions · 24 stateful · 2026-09-05 01:11:10 UTC
Parallelism
93/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,051,172 · 27 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
5w06w110w016w017w018w122w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x556a9a7a…b0ae
0x34b655…2a6f
4 touches
1 conflict
0xced4ddba…d164
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x4f125e89…7ee0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x53e08444…d671
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 0x556a9a7a4c…3bb0ae
Audit this contract →
← previous block·next block →recent activity