← previous blocknext block →recent activity
Analyzing
Block #102,103,864
14 transactions · 13 stateful · 2026-09-05 05:38:26 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,103,864 · 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
1w04w17w08w110w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x173b64af…6c43
0x34b655…2a6f
4 touches
1 conflict
0x2249932e…474a
0x34b655…2a6f
4 touches
1 conflict
0x30c777f3…bacc
0x34b655…2a6f
4 touches
1 conflict
0x4c9b66e1…e999
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x68055fa2…229e
0x34b655…2a6f
4 touches
1 conflict
0x76e02d19…7609
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 0x0ec07cf780…9cc0c9
Audit this contract →
← previous block·next block →recent activity