← previous blocknext block →recent activity
Analyzing
Block #102,506,159
16 transactions · 16 stateful · 2026-09-06 15:37:06 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,506,159 · 16 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
1w04w18w011w012w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x347817fd…9a4e
0x34b655…2a6f
4 touches
1 conflict
0x3b7dce3c…0531
0x34b655…2a6f
4 touches
1 conflict
0x9b4f173c…94e6
0x34b655…2a6f
4 touches
1 conflict
0xa6e7f29c…5d8c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002d
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 0x347817fd38…4e9a4e
Audit this contract →
← previous block·next block →recent activity