← previous blocknext block →recent activity
Analyzing
Block #102,018,295
22 transactions · 21 stateful · 2026-09-04 22:24:38 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,018,295 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w26w08w114w215w116w218w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x232b0b19…d946
0x34b655…2a6f
4 touches
1 conflict
0x3e50dd4c…05c7
0x34b655…2a6f
4 touches
1 conflict
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x19d98b4e…a9cf
0x065c9d…c394
3 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
3 conflicts on slot 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity