← previous blocknext block →recent activity
Analyzing
Block #102,243,183
19 transactions · 17 stateful · 2026-09-05 17:24:29 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,243,183 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w08w19w010w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0xb9a0dde5…9e2b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
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 0xe5bb3628b5…71e5e8
Audit this contract →
← previous block·next block →recent activity