← previous blocknext block →recent activity
Analyzing
Block #102,481,539
111 transactions · 86 stateful · 2026-09-06 13:32:07 UTC
Parallelism
87/100
Blocked
67%
Avg conflicts / tx
2.55
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #102,481,539 · 111 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w07w013w014w118w020w121w222w323w424w525w626w727w828w229w131w157w958w1070w176w177w982w1085w1187w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
28 touches
91 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0xaad6be10…0801
0x2a68ba…90c5
20 touches
45 conflicts
0x00000000…003d
0x065c9d…c394
20 touches
45 conflicts
0x892daf6e…48d8
0x065c9d…c394
20 touches
45 conflicts
0x5f77d607…2c84
0x065c9d…c394
18 touches
36 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
16 touches
28 conflicts
0xea02471d…1542
0x34b655…2a6f
16 touches
28 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: 0xf5b5f7f8…a36d70
91 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity