← previous blocknext block →recent activity
Analyzing
Block #102,205,726
23 transactions · 23 stateful · 2026-09-05 14:14:46 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,205,726 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w06w07w39w110w211w312w417w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b0621ee…3c2c
0x284f45…7777
8 touches
6 conflicts
0xd868fb65…3b4a
0xe1c8b7…3022
8 touches
6 conflicts
0xa164d951…1534
0xe1c8b7…3022
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0004
0x7aed55…0617
8 touches
6 conflicts
0xdf409966…6b16
0x3bd359…433a
8 touches
6 conflicts
0x4eb758b8…b13b
0x3bd359…433a
8 touches
6 conflicts
0x44ed742f…63f5
0x3bd359…433a
8 touches
6 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: 0x284f45fa…de7777
6 conflicts on slot 0x5b0621ee5a…623c2c
Audit this contract →
← previous block·next block →recent activity