← previous blocknext block →recent activity
Analyzing
Block #102,347,654
19 transactions · 18 stateful · 2026-09-06 02:13:50 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,347,654 · 19 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
5w06w110w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x173b64af…6c43
0x34b655…2a6f
4 touches
1 conflict
0x3f5831e5…02b2
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0x7c6f8cd0…2df5
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0x14ea9ada…e627
0x34b655…2a6f
2 touches
0 conflicts
0x14ea9ada…e628
0x34b655…2a6f
2 touches
0 conflicts
0x20492d53…80f9
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 0x173b64af39…0f6c43
Audit this contract →
← previous block·next block →recent activity