← previous blocknext block →recent activity
Analyzing
Block #102,436,684
19 transactions · 19 stateful · 2026-09-06 09:44:51 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.84
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,436,684 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w08w110w011w112w213w314w115w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05a4856d…d568
0x34b655…2a6f
8 touches
6 conflicts
0xd5982776…4846
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x640c4fb2…044a
0x34b655…2a6f
6 touches
3 conflicts
0x1a5de8bb…7bc7
0x34b655…2a6f
6 touches
3 conflicts
0x8a79b23e…0d95
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x05a4856d51…9ed568
Audit this contract →
← previous block·next block →recent activity