← previous blocknext block →recent activity
Analyzing
Block #102,104,575
14 transactions · 13 stateful · 2026-09-05 05:42:02 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,104,575 · 14 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
1w02w16w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a9e408e…3721
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xcd93b2d2…30e6
0x34b655…2a6f
4 touches
1 conflict
0xff3ed4c7…82e9
0x34b655…2a6f
4 touches
1 conflict
0x4432679f…7a5c
0x34b655…2a6f
4 touches
1 conflict
0x7332c051…a007
0xd32edf…ff58
3 touches
1 conflict
0x45f562b2…9294
0x34ae4d…3fc5
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 0x6a9e408e97…fb3721
Audit this contract →
← previous block·next block →recent activity