← previous blocknext block →recent activity
Analyzing
Block #102,246,163
16 transactions · 15 stateful · 2026-09-05 17:39:34 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,246,163 · 16 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
1w02w16w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19f8e68c…4f86
0x34b655…2a6f
4 touches
1 conflict
0x1d821a69…b822
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda17b98d…c3e1
0x34b655…2a6f
4 touches
1 conflict
0x2249932e…474a
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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 0x19f8e68cb7…a24f86
Audit this contract →
← previous block·next block →recent activity