← previous blocknext block →recent activity
Analyzing
Block #102,569,211
21 transactions · 17 stateful · 2026-09-06 20:56:50 UTC
Parallelism
90/100
Blocked
24%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,569,211 · 21 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
1w012w013w115w017w118w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xd5982776…4846
0x34b655…2a6f
4 touches
1 conflict
0x57070322…bc66
0xe52b14…7230
4 touches
1 conflict
0x28b01e5f…ced6
0xb754ba…508d
4 touches
1 conflict
0x28b01e5f…ced5
0xb754ba…508d
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x0bc75cf1…2cd2
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
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 0xb75367ffdb…6fa2b7
Audit this contract →
← previous block·next block →recent activity