← previous blocknext block →recent activity
Analyzing
Block #102,098,434
34 transactions · 27 stateful · 2026-09-05 05:10:52 UTC
Parallelism
85/100
Blocked
56%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,098,434 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w29w010w016w317w119w320w021w122w223w225w426w327w330w131w132w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x4aa2c9a7…107b
0x065c9d…c394
8 touches
6 conflicts
0x77ed432f…fa04
0x065c9d…c394
8 touches
6 conflicts
0x95523e2a…4c01
0x065c9d…c394
8 touches
6 conflicts
0x10a5a231…be40
0x34b655…2a6f
8 touches
6 conflicts
0x1ad84949…0fc1
0x34b655…2a6f
8 touches
6 conflicts
0x06e40499…165e
0x34ae4d…3fc5
6 touches
3 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity