← previous blocknext block →recent activity
Analyzing
Block #102,219,487
19 transactions · 19 stateful · 2026-09-05 15:24:21 UTC
Parallelism
63/100
Blocked
42%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,219,487 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w28w310w411w012w114w515w618w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xe108b282…58b3
0x34b655…2a6f
10 touches
10 conflicts
0x3462f1c7…1c3c
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity