← previous blocknext block →recent activity
Analyzing
Block #102,248,108
17 transactions · 12 stateful · 2026-09-05 17:49:25 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,248,108 · 17 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
2w03w17w011w013w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19f8e68c…4f86
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x310b970b…b1b3
0x34b655…2a6f
4 touches
1 conflict
0x3ed1f029…0a2d
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x67043b0b…97d7
0x34b655…2a6f
4 touches
1 conflict
0x7e273bc0…5dbc
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 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
1 conflict on slot 0x19f8e68cb7…a24f86
Audit this contract →
← previous block·next block →recent activity