← previous blocknext block →recent activity
Analyzing
Block #102,107,334
36 transactions · 26 stateful · 2026-09-05 05:56:01 UTC
Parallelism
81/100
Blocked
58%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,107,334 · 36 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
2w09w110w011w213w314w415w016w017w118w219w320w427w128w531w632w633w134w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x00000000…0002
0xf5b5f7…6d70
12 touches
15 conflicts
0x95523e2a…4c01
0x065c9d…c394
10 touches
10 conflicts
0x77ed432f…fa04
0x065c9d…c394
8 touches
6 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity