← previous blocknext block →recent activity
Analyzing
Block #102,224,729
16 transactions · 12 stateful · 2026-09-05 15:50:50 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,224,729 · 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
6w012w013w114w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6b5aec8…09bc
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x256918f1…c4d0
0x34b655…2a6f
4 touches
1 conflict
0x3d504fd9…e9a4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xbceecf11…0120
0x34b655…2a6f
4 touches
1 conflict
0xc00be471…2449
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 0xf6b5aec8de…8109bc
Audit this contract →
← previous block·next block →recent activity