← previous blocknext block →recent activity
Analyzing
Block #102,526,181
19 transactions · 18 stateful · 2026-09-06 17:18:37 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,526,181 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w08w09w111w116w117w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d0c4a4…add3
0x34b655…2a6f
8 touches
6 conflicts
0x8e0b06d1…5f32
0x34b655…2a6f
6 touches
3 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3d13406e…eff1
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
6 conflicts on slot 0x66d0c4a46b…adadd3
Audit this contract →
← previous block·next block →recent activity