← previous blocknext block →recent activity
Analyzing
Block #102,345,715
89 transactions · 85 stateful · 2026-09-06 02:04:02 UTC
Parallelism
98/100
Blocked
4%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,345,715 · 89 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w113w014w187w088w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x729c91b8…9539
0x188d58…ea8e
2 touches
0 conflicts
0x06e40499…165e
0x34ae4d…3fc5
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
2 touches
0 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: Perpl
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity