← previous blocknext block →recent activity
Analyzing
Block #102,192,394
14 transactions · 13 stateful · 2026-09-05 13:07:08 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,192,394 · 14 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08c5d8d8…c7c1
0x34b655…2a6f
4 touches
1 conflict
0x34e61077…195a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
2 touches
0 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x29a58269…011a
0x34b655…2a6f
2 touches
0 conflicts
0x2c062142…d50c
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 0x08c5d8d885…b9c7c1
Audit this contract →
← previous block·next block →recent activity