← previous blocknext block →recent activity
Analyzing
Block #102,205,131
20 transactions · 20 stateful · 2026-09-05 14:11:45 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,205,131 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w26w07w38w09w012w115w016w118w019w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa164d951…1534
0xe1c8b7…3022
8 touches
6 conflicts
0x5b0621ee…3c2c
0x284f45…7777
8 touches
6 conflicts
0x4eb758b8…b13b
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0004
0x7aed55…0617
8 touches
6 conflicts
0x44ed742f…63f5
0x3bd359…433a
8 touches
6 conflicts
0xdf409966…6b16
0x3bd359…433a
8 touches
6 conflicts
0xd868fb65…3b4a
0xe1c8b7…3022
8 touches
6 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 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: 0xe1c8b733…e33022
6 conflicts on slot 0xa164d95170…fa1534
Audit this contract →
← previous block·next block →recent activity