← previous blocknext block →recent activity
Analyzing
Block #106,191,459
19 transactions · 18 stateful · 2026-09-19 13:40:36 UTC
Parallelism
89/100
Blocked
28%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,191,459 · 19 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
2w03w14w05w06w18w09w113w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fff3d04…b5fd
0x34b655…2a6f
4 touches
1 conflict
0xb6ca29c6…1e2e
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x16586475…53db
0x99c7a7…8bf0
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 0x9fff3d04ab…8fb5fd
Audit this contract →
← previous block·next block →recent activity