← previous blocknext block →recent activity
Analyzing
Block #105,445,387
15 transactions · 14 stateful · 2026-09-16 23:03:12 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,445,387 · 15 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
2w03w16w010w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9abfeb11…cde8
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x2d127bff…143f
0x34b655…2a6f
2 touches
0 conflicts
0x2f17174f…68b4
0x34b655…2a6f
2 touches
0 conflicts
0x38cce915…c9a0
0x34b655…2a6f
2 touches
0 conflicts
0x51fc8795…126f
0x34b655…2a6f
2 touches
0 conflicts
0x74e92f81…d4b2
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity